3. Configuration¶
Backends required by Ferda are configured in .conf
files.
There will be example configuration files included
(fred-registry-services.conf.example
and
fred-logger-services.conf.example
).
3.1. Environment¶
Ferda’s behaviour can be modified by configuring the following variables in the .env
file in the directory from
which docker-compose
is run:
Name |
Default value |
Description |
---|---|---|
|
|
List of names and e-mails with names separated from e-mails by colons and individual admins separated by commas
(e.g. |
|
|
Comma-separated list of hosts; this variable needs to be set, unless you are in DEBUG mode. Otherwise, you will not be able to access Ferda on any hostname. |
|
|
Very important variable defining the connection with database; it is highly recommended to change the default
value, otherwise the database gets lost when the container is deleted; format for PostgreSQL is
|
|
|
Enabling/disabling debug mode; true/false |
|
|
Various e-mail settings (more details at https://docs.djangoproject.com/en/dev/ref/settings/) |
|
|
Logging server address |
|
required |
Configuration, address and port of the server running |
|
|
Enabling/disabling two-factor authentication via FIDO2 tokens; true/false |
|
|
system language |
|
|
List of available languages, format is similar as |
|
|
LDAP configuration variables (see https://github.com/etianen/django-python3-ldap); authentication via LDAP is
enabled only when the |
|
required |
Long random string; sensitive data |
|
|
Age of session cookie; the user will be automatically logged out after this period of inactivity (in seconds). |
|
|
Enabling/disabling session saving after every request; true/false |
|
|
Time zone |