khanh.pndc/nextcloud-docs
1
0
Fork 0
mirror of https://github.com/nextcloud/documentation.git synced 2026-01-03 10:20:02 +07:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2391 from owncloud/ostack

Browse Source 
add missing S3 parameter
This commit is contained in:
Carla Schroder
2016-04-27 12:06:44 -07:00
parent 65d7097e15 2cacc23742
commit 52982e345d
1 changed files with 14 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
admin_manual/enterprise_external_storage/s3_swift_as_primary_object_store_configuration.rst
View File

@@ -3,23 +3,21 @@ Configuring S3 and OpenStack Swift Objects as Primary Storage
=============================================================
In ownCloud Enterprise Subscription, you can configure S3 objects as primary
storage. This replaces the default data directory, which is
``/var/www/owncloud/data`` on default Linux installations, and
``C:\inetpub\wwwroot\owncloud\data`` on Windows servers. However, you may need
to keep the ``data/`` directory for these reasons:
storage. This replaces the default ownCloud ``owncloud/data`` directory. You may
still need to keep the ``owncloud/data`` directory for these reasons:
* The ownCloud log file is saved in the data directory
* Legacy apps may not support using anything but the ``data/`` directory
* Legacy apps may not support using anything but the ``owncloud/data`` directory
You can move your logfile by changing its location in ``config.php``. You may still need
``data/`` for backwards compatibility with some apps.
``owncloud/data`` for backwards compatibility with some apps.
Implications
------------
It is important to note that ownCloud in object store mode will expect exclusive
access to the object store container, because it only stores the binary data
for each file. The metadata is currently kept in the local database for
performance reasons.
ownCloud in object store mode expects exclusive access to the object store
container, because it only stores the binary data for each file. The metadata
are kept in the local database for performance reasons.
The current implementation is incompatible with any app that uses
direct file I/O and circumvents the ownCloud virtual filesystem. That includes
@@ -29,8 +27,9 @@ to be fetched in addition to any requested file.
Configuration
-------------
Look in ``config.sample.php`` for a example configurations. Copy the
relevant part to your ``config.php`` file. Any objectstore needs to implement
relevant part to your ``config.php`` file. Any object store needs to implement
``\\OCP\\Files\\ObjectStore\\IObjectStore`` and can be passed parameters in the
constructor with the ``arguments`` key:
@@ -45,6 +44,7 @@ constructor with the ``arguments`` key:
Amazon S3
~~~~~~~~~
The S3 backend mounts a bucket of the Amazon S3 object store
into the virtual filesystem. The class to be used is ``OCA\ObjectStore\S3``:
@@ -56,12 +56,14 @@ into the virtual filesystem. The class to be used is ``OCA\ObjectStore\S3``:
'key' => 'yourkey',
'secret' => 'yoursecret',
'bucket' => 'your-oc-bucket',
'region' => 'region-of-your-oc-bucket'
),
),
Ceph S3
~~~~~~~
The S3 backend can also be used to mount the bucket of a ceph object store via the s3 API
into the virtual filesystem. The class to be used is ``OCA\ObjectStore\S3``:
@@ -83,6 +85,7 @@ into the virtual filesystem. The class to be used is ``OCA\ObjectStore\S3``:
OpenStack Swift
~~~~~~~~~~~~~~~
The Swift backend mounts a container on an OpenStack Object Storage server
into the virtual filesystem. The class to be used is ``\\OC\\Files\\ObjectStore\\Swift``: