Config options are mostly passed to Indigo as environment variables. These are the options you can set:
Required for production. The AWS access key ID for the account with write-access to the S3 bucket used for storing attachments.
Required for production. The AWS secret access key for the account with write-access to the S3 bucket used for storing attachments.
Required for production. The name of the S3 bucket for storing attachments.
The regional S3 endpoint to use. Optional. Default:
Required. The URL of the database to use
DEBUGsetting. Everything other than
truemeans False. This should always be
falsein production. Default:
DEFAULT_FROM_EMAILsetting: who do emails come from? Uses
EMAIL_HOSTsetting. The SMTP host through which to send user emails such as password resets.
EMAIL_HOST_PASSWORDsetting. The SMTP password.
EMAIL_HOST_PORTsetting. The SMTP port (default: 25).
EMAIL_HOST_USERsetting. The SMTP username.
Required if DJANGO_DEBUG is not true. The Django
SECRET_KEYsetting. In production you should use a random (and secret) string.
Google Analytics ID for website tracking. Only used when
Required Email address users can email for help.
Should email sending fail silently?
JSON of Google Sheets API credentials token details, if you want Indigo to be able to talk to Google Sheets directly. Otherwise, Indigo will use CSV export and the Google Sheet will need to be publicly accessible.
For details on setting up Google Sheets for API access, see https://medium.com/@denisluiz/python-with-google-sheets-service-account-step-by-step-8f74c26ed28e
Should notification emails be sent asynchronously in the background? Default is False. See django-background-tasks documentation.