Clarify which docker-compose.yaml to use
Starting from ``UPGRADING.md`` I didn't realize there were "examples" below "deployment". I suggest making it explicit here.
This commit is contained in:
parent
724e48f738
commit
33a8706109
11
UPGRADING.md
11
UPGRADING.md
|
@ -11,11 +11,12 @@ explicitly. Once we implement them, their usage will be described in the
|
|||
* Shut down all services
|
||||
* Obviously, now is a good time to perform a full backup ;)
|
||||
* Update the codebase (`git pull`, `git submodule update`).
|
||||
* Update docker-compose.yaml from the example. Leave the MongoDB service in
|
||||
place for now, but update all other service descriptions. You can remove
|
||||
`redis` already. Generate a better password than the default for your
|
||||
postgres user. Traefik rules have been simplified as all routes are handled
|
||||
by the portal service now.
|
||||
* Update your ``docker-compose.yaml`` from the ``deployment/examples`` folder.
|
||||
* Leave the MongoDB service in place for now
|
||||
* but update all other service descriptions.
|
||||
* You can remove `redis` already. Generate a better password than the default for your
|
||||
postgres user. Traefik rules have been simplified as all routes are handled
|
||||
by the portal service now.
|
||||
* Start up the `mongo` and `postgres` services. Wait for postgres to finish
|
||||
initializing (see [README](README.md)).
|
||||
* Build the new image (e.g. with `docker-compose build portal`)
|
||||
|
|
Loading…
Reference in a new issue