From f1d21f518aab36f490ec96cbc5477db8b9a90edf Mon Sep 17 00:00:00 2001 From: Markus Frosch Date: Thu, 31 Dec 2015 17:12:54 +0100 Subject: [PATCH] owncloud: Update docs for volume persistence resolves docker-library/owncloud#22 --- owncloud/content.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/owncloud/content.md b/owncloud/content.md index 20b427fb8..9e0201b59 100644 --- a/owncloud/content.md +++ b/owncloud/content.md @@ -18,6 +18,20 @@ $ docker run -d -p 80:80 owncloud:8.1 Then go to http://localhost/ and go through the wizard. By default this container uses SQLite for data storage, but the wizard should allow for connecting to an existing database. Additionally, tags for 6.0, 7.0, or 8.0 are available. +For a MySQL database you can link an database container, e.g. `--link my-mysql:mysql`, and then use `mysql` as the database host on setup. + +## Persistent data + +All data is stored within the default volume `/var/www/html`. With this volume, ownCloud will only be updated when the file `version.php` is not present. + +- `-v /:/var/www/html` + +For fine grained data persistence, you can use 3 volumes, as shown below. + +- `-v //apps:/var/www/html/apps` installed / modified apps +- `-v //config:/var/www/html/config` local configuration +- `-v //data:/var/www/html/data` the actual data of your ownCloud + ### Caveat When using the 6.0 image, you need to map the host port to the container port that apache listens on when going through the installation wizard. By default, this is port 80.