... | ... | @@ -2,9 +2,9 @@ |
|
|
It is recommended to read this in full before doing anything!
|
|
|
Every step in [docker install](docker-install) should be done.
|
|
|
|
|
|
First make sure to create a production.yml file corresponding to your needs, see [the docker-compose docs](https://docs.docker.com/compose/). This file will be used in conjunction with the default docker-compose.yml file, an example is given, you can copy it as a bootstrap for your own.
|
|
|
First make sure to create a docker-compose.override.yml file corresponding to your needs, see [the docker-compose docs](https://docs.docker.com/compose/). This file will be used in conjunction with the default docker-compose.yml file, an example is given, you can copy it as a bootstrap for your own.
|
|
|
|
|
|
$ cp production.yml{_example,}
|
|
|
$ cp docker-compose.override.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.
|
... | ... | @@ -32,13 +32,13 @@ Alternatively you can create a file called `.env` and write those variables in i |
|
|
|
|
|
$ git pull origin master
|
|
|
|
|
|
### Build:
|
|
|
## Pull the images:
|
|
|
|
|
|
$ docker-compose -f docker-compose.yml -f production.yml build --build-arg VERSION_DATE="$(git describe --tags) $(git log -1 --format=%ad)"
|
|
|
$ docker-compose pull
|
|
|
|
|
|
### Run:
|
|
|
### Run everything:
|
|
|
|
|
|
$ docker-compose -f docker-compose.yml -f production.yml up -d
|
|
|
$ docker-compose up -d
|
|
|
|
|
|
### Setting the domain name:
|
|
|
|
... | ... | |