From b5d93ab354aa4177495e67b552bb1317f9865d92 Mon Sep 17 00:00:00 2001 From: Robert Pocklington Date: Tue, 18 Jan 2022 14:28:36 +1100 Subject: [PATCH] Change outdated documentation ("owncloud" driver is not the default) --- docs/extensions/storage/storagedrivers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/extensions/storage/storagedrivers.md b/docs/extensions/storage/storagedrivers.md index fb83e21ca..70afc19d9 100644 --- a/docs/extensions/storage/storagedrivers.md +++ b/docs/extensions/storage/storagedrivers.md @@ -141,7 +141,7 @@ To provide the other storage aspects we plan to implement a FUSE overlay filesys The owncloud storage driver was used for testing purposes early on. For a parallel deployment focus has shifted to the owncloudsql. {{< /hint >}} -This is the current default storage driver. While it implements the file tree (using redis, including id based lookup), ETag propagation, trash, versions and sharing (including expiry) using the data directory layout of ownCloud 10 it has [known limitations](https://github.com/owncloud/core/issues/28095) that cannot be fixed without changing the actual layout on disk. +While this storage driver implements the file tree (using redis, including id based lookup), ETag propagation, trash, versions and sharing (including expiry) using the data directory layout of ownCloud 10 it has [known limitations](https://github.com/owncloud/core/issues/28095) that cannot be fixed without changing the actual layout on disk. To setup it up properly in a distributed fashion, the storage-home and the storage-oc need to share the same underlying FS. Their "data" counterparts also need access to the same shared FS. For a simple docker-compose setup, you can create a volume which will be used by the "storage-storage-home", "storage-storage-home-data", "storage-storage-oc" and "storage-storage-oc-data" containers. Using the `owncloud/ocis` docker image, the volume would need to be hooked in the `/var/lib/ocis` folder inside the containers.