From 33a87061098911ea9b0da8f2f2d34b0ec1a63e32 Mon Sep 17 00:00:00 2001
From: gluap <44007906+gluap@users.noreply.github.com>
Date: Fri, 3 Dec 2021 22:01:59 +0100
Subject: [PATCH] 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.
---
 UPGRADING.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/UPGRADING.md b/UPGRADING.md
index 42aa9e2..9623f2e 100644
--- a/UPGRADING.md
+++ b/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`)