summaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorJonas Thelemann <e-mail@jonas-thelemann.de>2019-02-20 01:51:46 +0100
committerMarc Brückner <marc@ma-br.de>2019-02-25 19:00:46 +0100
commitd9ca9e4b08e416ae8a72db0a8b3dc847dcdbf490 (patch)
tree8931442a35a416d78da0c5bf04ea9268bbef12f9 /README.md
parent1091814e9b06c8a66d0e3583bb12c591434aeccb (diff)
Rephrase README's "Named Volumes" Paragraph
Signed-off-by: Jonas Thelemann <e-mail@jonas-thelemann.de>
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index b6c0876c..84b5bfbe 100644
--- a/README.md
+++ b/README.md
@@ -43,7 +43,7 @@ By default this container uses SQLite for data storage, but the Nextcloud setup
## Persistent data
The Nextcloud installation and all data beyond what lives in the database (file uploads, etc) is stored in the [unnamed docker volume](https://docs.docker.com/engine/tutorials/dockervolumes/#adding-a-data-volume) volume `/var/www/html`. The docker daemon will store that data within the docker directory `/var/lib/docker/volumes/...`. That means your data is saved even if the container crashes, is stopped or deleted.
-To make your data persistent to upgrading and get access for backups is using named docker volume or mount a host folder. To achieve this you need one volume for your database container and Nextcloud.
+A named Docker volume or a mounted host directory should be used for upgrades and backups. To achieve this you need one volume for your database container and one for Nextcloud.
Nextcloud:
- `/var/www/html/` folder where all nextcloud data lives