Document how to update installations

[maxking]

The documentation steps are simple:

$ docker-compose stop
$ docker-compose rm
$ docker pull maxking/mailman-core:$tag
$ docker pull maxking/mailman-web:$tag
$ docker-compose up -d

Make sure that you use the appropriate -f docker-compose.yaml file in all the above commands.

[brianemwd]

Do I need to replace the $tag with: 0.2 or 0.2.1

(Edit response by Abhilash to remove extra whitespace)

[maxking]

You can use either, both of them point to same image. 0.2 is a moving target and the next time I publish a 0.2.x image, 0.2 will point to that (always the latest version of 0.2.x).

[brianemwd]

You might want to add to the bottom of the update instructions: $ docker-compose start mailman-core $ docker-compose start mailman-web

[maxking]

On January 25, 2019 8:27:33 PM PST, brianemwd [email protected] wrote:

You might want to add to the bottom of the update instructions: $ docker-compose start mailman-core $ docker-compose start mailman-web

Docker-compose up -d

That should take care of starting all services.

Sent from my Android device with K-9 Mail. Please excuse my brevity.

[brianemwd]

That is what I thought as well but when I accessed Postorius I got a REST API error saying I needed to start mailman-core.

[maxking]

How long did you wait for? It usually takes anywhere between 10 to 30 seconds to bring up the REST Runners.

You can check if the container itself came up by running docker ps. According to the docs, docker-compose up should take care of bringing up the containers. (-d flag makes it run in background)

[brianemwd]

That is a good point. I did not wait very long at all. I will do that next time there is an update/upgrade. Great help, thanks!

[github-actions[bot]]

This issue has not been updated for more than 1year