Preparation

This is where the service will store its own application data and ensures we can quickly update the service image.

Ensure your user has permissions to access the folder.

This is the user name that will be used behind the scenes to log into the database.

For example: fider_admin

This is the URL that the service will be hosted and accessible through.

For example: fider.example.com

This is the email address that will be attached to email notifications and should not be replied to because the inbox is not monitored or is non existent. 

For example: noreply@fider.example.com

This is the host address of your email server.

For example: smtp.gmail.com

This is the port used by your email server.

For example: 587

This is the account user name used by your email server.

For example: example@gmail.com

This enables StartTLS, which is used by the email server to upgrade insecure connections to one using TLS or SSL.

Recommended: true

This is the password that will be used for root access to the database.

It is important to use secure, randomly generated password.

You can use a random alphanumeric string from a password manager, or open the terminal and run the command:

tr -dc 'A-Za-z0-9!"#$%&'\''()*+,-./:;<=>?@[\]^_`{|}~' </dev/urandom | head -c 32; echo

This pulls a random string from the 'urandom' device, removes unwanted characters and trim it to an appropriate length.

This is the secret that will be used for validating users who are logged into the service.

It is important to use secure, randomly generated token.

You can use a random alphanumeric string from a password manager, or open the terminal and run the command:

tr -dc 'A-Za-z0-9!' </dev/urandom | head -c 32; echo

This pulls a random string from the 'urandom' device, removes unwanted characters and trim it to an appropriate length.

This is the password for logging into your email account for sending administrative notifications. 

When possible, you should use app passwords.