Skip to content

Commit af46dc5

Browse files
committed
README: Document updating docker-compose.yml.
1 parent 9d866d7 commit af46dc5

File tree

1 file changed

+13
-5
lines changed

1 file changed

+13
-5
lines changed

README.md

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -390,17 +390,25 @@ section.
390390
`volumes` lines in `docker-compose.yml`
391391
e.g. `/opt/docker/zulip/postgresql/data/`.
392392

393-
1. Pull the new image version, e.g. for `2.0.1` run: `docker pull
394-
zulip/docker-zulip:2.0.1-0`.
395-
396-
2. Edit your `docker-compose.yml` to point to the new image version,
393+
1. Pull the new image version, e.g. for `2.0.8` run: `docker pull
394+
zulip/docker-zulip:2.0.8-0`. We recommend always upgrading to the
395+
latest minor release within a major release series.
396+
397+
2. Update this project to the corresponding `docker-zulip` version and
398+
resolve any merge conflicts in `docker-compose.yml`.
399+
This is important as new Zulip releases may require additional
400+
settings to be specified in `docker-compose.yml`
401+
(E.g. authentication settings for `memcached` became mandatory in
402+
the `2.1.2` release).
403+
404+
3. Verify that your updated `docker-compose.yml` points to the desired image version,
397405
e.g.:
398406
```yml
399407
zulip:
400408
image: "zulip/docker-zulip:2.0.1-0"
401409
```
402410
403-
3. You can execute the upgrade by running:
411+
4. You can execute the upgrade by running:
404412
405413
```
406414
# Stops the old zulip container; this beings your downtime

0 commit comments

Comments
 (0)