schleuder.yml 2.63 KB
Newer Older
1
# Where are the list-directories stored (contain log-files and GnuPG-keyrings).
paz's avatar
paz committed
2
lists_dir: /var/lib/schleuder/lists
3

4
# Where to write list-logs. The actual log-file will be <lists_logs_base_dir>/<hostname>/<listname>/list.log.
paz's avatar
paz committed
5
listlogs_dir: /var/lib/schleuder/lists
6

7
# Schleuder reads plugins also from this directory.
paz's avatar
paz committed
8
plugins_dir: /etc/schleuder/plugins
9

10 11 12 13 14 15 16 17 18
# Schleuder reads filters also from this directory path,
# in the specific pre_decryption or post_decryption subdirectory.
# Filter files must follow the following convention for the
# filename: \d+_a_name.rb
# Where \d+ is any number, that defines the place in the
# list of filters and a_name must match the method name
# of the filter.
# The built-in filters are using round numbers for their
# positioning within the list. Increased by ten.
19
filters_dir: /usr/local/lib/schleuder/filters
20

21
# How verbose should Schleuder log to syslog? (list-specific messages are written to the list's log-file).
paz's avatar
paz committed
22
log_level: warn
23

24 25 26 27 28 29
# Which keyserver to refresh keys from (used by `schleuder refresh_keys`, meant
# to be run from cron weekly).
# If you have gnupg 2.1, we strongly suggest to use a hkps-keyserver:
#keyserver: hkps://hkps.pool.sks-keyservers.net
# If you have gnupg 2.1 and TOR running locally, use a onion-keyserver:
#keyserver: hkp://jirk5u4osbsr34t5.onion
30 31 32
# If you have an OS-wide defined keyserver, specify a blank value to have that
# one used:
#keyserver: 
33 34 35
# The default works for all supported versions of gnupg:
keyserver: pool.sks-keyservers.net

36 37 38 39 40 41 42
# Who is maintaining the overall schleuder installation and should be
# notified about severe problems with lists.
# This address should be a postmaster-like account, especially it should
# not be another schleuder list.
# Is also used as an envelope sender of admin notifications.
superadmin: root@localhost

43
# For these options see documentation for ActionMailer::smtp_settings, e.g. <http://api.rubyonrails.org/classes/ActionMailer/Base.html>.
44
smtp_settings:
45
  address: localhost
46 47 48 49 50 51 52
  port: 25
  #domain:
  #enable_starttls_auto:
  #openssl_verify_mode:
  #authentication:
  #user_name:
  #password:
53 54

# The database to use. Unless you want to run the tests you only need the `production`-section.
paz's avatar
paz committed
55 56 57
database:
  production:
    adapter:  'sqlite3'
paz's avatar
paz committed
58
    database: /var/lib/schleuder/db.sqlite
paz's avatar
paz committed
59
    timeout: 5000
60 61

api:
62
  host: localhost
63
  port: 4443
paz's avatar
paz committed
64
  # Certificate and key to use. You can create new ones with `schleuder cert generate`.
65 66 67 68 69 70 71 72
  tls_cert_file: /etc/schleuder/schleuder-certificate.pem
  tls_key_file: /etc/schleuder/schleuder-private-key.pem
  # List of api_keys to allow access to the API.
  # Example:
  # valid_api_keys:
  #   - abcdef...
  #   - zyxwvu...
  valid_api_keys: