Fixes #810: Clarify docker-compose upgrade

Adds a better working procedure for upgrades. Mention DB migration using docker-compose.

Signed-off-by: Daniel Helgenberger <daniel.helgenberger@m-box.de>
This commit is contained in:
Daniel Helgenberger 2019-07-26 13:19:41 +02:00
parent 060cf0883f
commit 5f26f842c3
No known key found for this signature in database
GPG Key ID: 28A07B8B57F2FC42
1 changed files with 8 additions and 3 deletions

View File

@ -284,9 +284,15 @@ When using docker-compose your compose file takes care of your configuration, so
```console
$ docker-compose pull
$ docker-compose build
$ docker-compose up -d
```
After the container is started up, run the database migrations:
```console
$ docker-compose exec --user www-data app php occ db:add-missing-indices
```
# Adding Features
A lot of people want to use additional functionality inside their Nextcloud installation. If the image does not include the packages you need, you can easily build your own image on top of it.
@ -336,12 +342,11 @@ docker run -d your-name
or for docker-compose:
```console
docker-compose build --pull
docker-compose pull
docker-compose build
docker-compose up -d
```
The `--pull` option tells docker to look for new versions of the base image. Then the build instructions inside your `Dockerfile` are run on top of the new image.
# Migrating an existing installation
You're already using Nextcloud and want to switch to docker? Great! Here are some things to look out for: