Add documentation for upgradeing and data persistence

[zulip]

Add documentation for upgradeing and data persistence

[galexrt]

The default way using the docker-compose.yml is that in zulip uploaded files are saved in a volume on the host.
All other cotainers do the same, save data to a volume on the host.

See https://github.com/Galexrt/docker-zulip/blob/master/docker-compose.yml#L51-L52

[reyman]

Ok, thanks, so to upgrade the images, what is the best way ?

[galexrt]

You stop your current running instance and then start with the new image(s).

For every new version there is an updated docker-compose.yml in the repo.

[reyman]

Some information about this process for upgrading image of zulip can be added in the documentation perhaps ?
Another related question for a noob like me, where is stores the image after a pull and how can i edit the yml file? I edit the wiki after that if you want.

[galexrt]

@reyman Yes you are right. Information about upgrading should be added to the documentation and README.md.

[galexrt]

@reyman I added a page about it. See https://github.com/Galexrt/docker-zulip/wiki/Upgrade-Zulip. Is it okay?

[reyman]

Great thx :)
There is another point that is not clear for noob like me, the first image init using docker-compose.

After the first pull image, user need to create a file docker-compose.yml in project directory and run docker build using from quay.io/galexrt/zulip:v1.3.9 isn't it ? I crosspost on docker, because i find trat documentation is not clear on this point.

[galexrt]

@reyman What do you mean with "... the first image init using docker-compose."?

You don't need to create a new docker-compose.yml. There is an example docker-compose.yml in the repository.
See https://github.com/Galexrt/docker-zulip/blob/master/docker-compose.yml.

Closing as of documentation has been added. You can still reply.

[reyman]

Ok i start to understand. Hum, but when i pull the image like you propose in documentation, this is not clear where the image is uploaded by docker (i'm using ubuntu). If i understand, after pull, and after i found the docker-compose.yml, i modify it, build and run the image and that's all ?

[galexrt]

@reyman You don't need to build the image. When you pull it you get a working image.
The docker-compose.yml just keeps the settings, when you run the image using docker-compose up.