... | ... | @@ -6,9 +6,14 @@ First make sure to create a production.yml file corresponding to your needs, see |
|
|
|
|
|
$ cp production.yml{_example,}
|
|
|
|
|
|
Make sure to set good values for cpus, mem_limit and mem_reservation on your workers services or the server will have poor performances and the users experience will be greatly degraded.
|
|
|
Be wary that docker stores everything in /var/lib/docker rather than the current path, so it's advisable to either override the volumes configuration or the whole docker data directory if your system partition is small.
|
|
|
|
|
|
Change at the very least the admin password and the secret key in the variables.env file **before building**!
|
|
|
Change at the very least the admin password (DJANGO_SU_PASSWORD) and the secret key (SECRET_KEY) in the variables.env file **before building**!
|
|
|
[SECRET_KEY](https://docs.djangoproject.com/en/3.0/ref/settings/#secret-key) is used for cryptographic signing, should be unique and unpredictable.
|
|
|
Change DJANGO_SU_EMAIL to receive error emails.
|
|
|
DJANGO_FROM_EMAIL is the sender of outbound emails.
|
|
|
|
|
|
The variables.env file is passed to the containers, some configurations need to be passed directly to the docker-compose build through environment variables on the host.
|
|
|
Configure exim (message transfer agent) with:
|
|
|
|
... | ... | |