... | ... | @@ -6,9 +6,9 @@ First make sure to create a production.yml file corresponding to your needs, see |
|
|
|
|
|
$ cp production.yml{_example,}
|
|
|
|
|
|
Be wary that docker does 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.
|
|
|
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 the admin password and the secret key in the variables.env file **before building**!
|
|
|
Change at the very least the admin password and the secret key in the variables.env file **before building**!
|
|
|
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:
|
|
|
|
... | ... | @@ -37,7 +37,7 @@ Alternatively you can create a file called `.env` and write those variables in i |
|
|
|
|
|
### Setting the domain name:
|
|
|
|
|
|
When sending emails we don't have access to the request, which means we don't know on which domain to generate urls for. You can set it up here: /admin/sites/site/.
|
|
|
When sending emails we don't always have access to the request, which means we don't know on which domain to generate urls for. You can set it up here: /admin/sites/site/.
|
|
|
It may become a build option at some point.
|
|
|
|
|
|
### Backing up the database:
|
... | ... | |