mirror of
https://github.com/nextcloud/documentation.git
synced 2026-01-03 18:26:42 +07:00
Split external storage backends to separate pages
This commit is contained in:
Robin McCorkell
@@ -0,0 +1,23 @@
|
||||
=========
|
||||
Amazon S3
|
||||
=========
|
||||
|
||||
All you need to connect your Amazon S3 buckets to ownCloud is your S3 Access
|
||||
Key, Secret Key, and your bucket name.
|
||||
|
||||
In the ``Folder name`` field enter the folder name that you want to appear on
|
||||
your ownCloud ``Files`` page.
|
||||
|
||||
In the ``Access Key`` field enter your S3 Access Key.
|
||||
|
||||
In the ``Secret Key`` field enter your S3 Secret Key.
|
||||
|
||||
In the ``Bucket`` field enter the name of your S3 bucket you want to share.
|
||||
|
||||
In the ``Available for`` field enter the users or groups who have permission to
|
||||
access your S3 mount.
|
||||
|
||||
The hostname, port, and region of your S3 server are optional; you will need
|
||||
to use these for non-Amazon S3-compatible servers.
|
||||
|
||||
.. figure:: ../../images/external-storage-amazons3.png
|
||||
@@ -0,0 +1,46 @@
|
||||
=======
|
||||
Dropbox
|
||||
=======
|
||||
|
||||
Connecting Dropbox is a little more work because you have to create a Dropbox
|
||||
app. Log into the `Dropbox Developers page <http://www.dropbox.com/developers>`_
|
||||
and click ``App Console``:
|
||||
|
||||
.. figure:: ../../images/external-storage-dropbox.png
|
||||
|
||||
If you have not already created any Dropbox apps it will ask you to accept
|
||||
their terms and conditions. Then you are presented with the choice to create
|
||||
either a Drop-ins App or a Dropbox API App. Click ``Dropbox API App``, and then
|
||||
check:
|
||||
|
||||
* Files and datastores.
|
||||
* No -- My app needs access to files already on Dropbox.
|
||||
* All file types -- My app needs access to a user's full Dropbox. Only
|
||||
supported via the CoreAPI.
|
||||
|
||||
Then enter whatever name you want for your app.
|
||||
|
||||
.. figure:: ../../images/external-storage-dropbox-app.png
|
||||
|
||||
Now click the ``Create App`` button. Under ``Status``, do not click
|
||||
``Development (Apply for production status)`` because that is for apps that you
|
||||
want to release publicly.
|
||||
|
||||
Click ``Enable additional users`` to allow multiple oC users to use your new
|
||||
Dropbox share.
|
||||
|
||||
Note your App key and App secret, which you will enter in the External Storage
|
||||
form on your ownCloud Admin page.
|
||||
|
||||
.. figure:: ../../images/external-storage-dropbox-configapp.png
|
||||
|
||||
Your ownCloud configuration requires only the local mount name, the App Key and
|
||||
the App Secret, and which users or groups have access to the share.
|
||||
|
||||
.. figure:: ../../images/external-storage-dropbox-oc.png
|
||||
|
||||
You must be logged into Dropbox, and when ownCloud successfully verifies your
|
||||
connection Dropbox will ask for verification to connect to your Dropbox
|
||||
account. Click ``Allow``, and you're done.
|
||||
|
||||
.. figure:: ../../images/external-storage-dropbox-allowshare.png
|
||||
24
admin_manual/configuration_files/external_storage/ftp.rst
Normal file
24
admin_manual/configuration_files/external_storage/ftp.rst
Normal file
@@ -0,0 +1,24 @@
|
||||
===
|
||||
FTP
|
||||
===
|
||||
|
||||
Connecting to an FTP server requires:
|
||||
|
||||
* Whatever name you want for your local mountpoint.
|
||||
* The URL of your FTP server, and optionally the port number.
|
||||
* FTP server username and password.
|
||||
* Remote Subfolder, the FTP directory to mount in ownCloud. ownCloud defaults to the root
|
||||
directory. When you specify a different directory you must leave off the
|
||||
leading slash. For example, if you want to connect your
|
||||
``public_html/images`` directory, then type it exactly like that.
|
||||
* Choose whether to connect in the clear with ``ftp://``, or to encrypt your
|
||||
FTP session with SSL/TLS over ``ftps://`` (Your FTP server must be
|
||||
configured to support ``ftps://``)
|
||||
* Enter the ownCloud users or groups who are allowed to access the share.
|
||||
|
||||
.. note:: The external storage ``FTP/FTPS`` needs the ``allow_url_fopen`` PHP
|
||||
setting to be set to ``1``. When having connection problems make sure that it is
|
||||
not set to ``0`` in your ``php.ini``.
|
||||
|
||||
.. figure:: ../../images/external-storage-ftp.png
|
||||
|
||||
87
admin_manual/configuration_files/external_storage/google.rst
Normal file
87
admin_manual/configuration_files/external_storage/google.rst
Normal file
@@ -0,0 +1,87 @@
|
||||
============
|
||||
Google Drive
|
||||
============
|
||||
|
||||
All applications that access a Google API must be registered through the
|
||||
`Google Cloud Console <https://console.developers.google.com/>`_. Follow along carefully
|
||||
because the Google interface is a bit of a maze and it's easy to get lost.
|
||||
|
||||
.. note:: Your ownCloud server must have a registered domain name and be
|
||||
accessible over the Internet; Google Drive will not connect to a LAN-only
|
||||
server.
|
||||
|
||||
If you already have a Google account, such as Groups, Drive, or Mail, you can
|
||||
use your existing login to log into the Google Cloud Console. After logging in
|
||||
click the ``Create Project`` button.
|
||||
|
||||
.. figure:: ../../images/external-storage-google-drive.png
|
||||
|
||||
Give your project a name, and either accept the default ``Project ID`` or create
|
||||
your own, then click the ``Create`` button.
|
||||
|
||||
.. figure:: ../../images/external-storage-google-drive1.png
|
||||
|
||||
The next screen is your ``Project Dashboard``. The Activities screen on the
|
||||
bottom left shows your current status. In the left sidebar click ``APIs
|
||||
& Auth > APIs``, and then click ``Google Apps APIs > Drive API``.
|
||||
|
||||
.. figure:: ../../images/external-storage-google-drive2.png
|
||||
|
||||
Before you click ``Enable API`` you might want to click on ``Learn more`` or
|
||||
``Explore this API``. Then click ``Enable API``.
|
||||
|
||||
.. figure:: ../../images/external-storage-google-drive3.png
|
||||
|
||||
``Enable API`` takes you to the Drive API dashboard, with tabs for
|
||||
``Overview, Usage, Quota``, and ``Drive UI Integration``. Feel free to
|
||||
explore, and then go to ``APIs & Auth > Credentials``. This screen has two
|
||||
sections: ``0Auth`` and ``Public API Access``.
|
||||
|
||||
.. figure:: ../../images/external-storage-google-drive4.png
|
||||
|
||||
|
||||
Click ``0Auth > Create New Client ID``. The next screen that opens is ``Create
|
||||
Client ID``. Check ``Web Application`` and click the ``Configure Consent
|
||||
Screen`` button. You'll see the consent screen the first time you create a
|
||||
mountpoint for your Google Drive in owncloud.
|
||||
|
||||
.. figure:: ../../images/external-storage-google-drive5.png
|
||||
|
||||
There are just a few required fields on the Consent Screen form: the email
|
||||
address of your Google account and your app name. The optional fields include
|
||||
your site URL, a link to your logo, and links to your privacy and terms of
|
||||
service policies. Your logo must be a hosted file because there is no upload
|
||||
dialogue. Click ``Save`` when you're finished.
|
||||
|
||||
.. figure:: ../../images/external-storage-google-drive6.png
|
||||
|
||||
Now you should be on the ``Edit Client Settings`` screen. The ``Authorized
|
||||
JavaScript Origins`` is your root domain, for example
|
||||
``https://www.example.com``. You need two ``Authorized Redirect URIs``, which
|
||||
must be in the following form::
|
||||
|
||||
https://example.com/owncloud/index.php/settings/personal
|
||||
https://example.com/owncloud/index.php/settings/admin
|
||||
|
||||
Replace ``https://example.com/owncloud/`` with your own ownCloud server URL,
|
||||
then click ``Save``.
|
||||
|
||||
.. figure:: ../../images/external-storage-google-drive10.png
|
||||
|
||||
This should take you back to the 0Auth screen, with a summary of your settings
|
||||
and editing buttons. This contains your ``Client ID`` and ``Client Secret``,
|
||||
which you need to set up your ownCloud connection.
|
||||
|
||||
.. figure:: ../../images/external-storage-google-drive11.png
|
||||
|
||||
Go to your ``Admin`` page in ownCloud, create your new folder name, enter the
|
||||
Client ID and Client Secret, select your users and groups, and click ``Grant
|
||||
Access``.
|
||||
|
||||
.. figure:: ../../images/external-storage-google-drive8.png
|
||||
|
||||
Google will open a dialogue asking for permission to connect to ownCloud. Click
|
||||
``Accept``. When you see the green light confirming a successful connection
|
||||
you're finished.
|
||||
|
||||
|
||||
18
admin_manual/configuration_files/external_storage/local.rst
Normal file
18
admin_manual/configuration_files/external_storage/local.rst
Normal file
@@ -0,0 +1,18 @@
|
||||
=====
|
||||
Local
|
||||
=====
|
||||
|
||||
Use this to mount any directory on your ownCloud server that is outside of your
|
||||
ownCloud ``data/`` directory. This directory must be readable and writable by
|
||||
your HTTP server user.
|
||||
|
||||
In the ``Folder name`` field enter the folder name that you want to appear on
|
||||
your ownCloud ``Files`` page.
|
||||
|
||||
In the ``Configuration`` field enter the full filepath of the directory you
|
||||
want to mount.
|
||||
|
||||
In the ``Available for`` field enter the users or groups who have permission to
|
||||
access the mount.
|
||||
|
||||
.. figure:: ../../images/external-storage-app-local.png
|
||||
@@ -0,0 +1,16 @@
|
||||
========================
|
||||
OpenStack Object Storage
|
||||
========================
|
||||
|
||||
Use this to mount a container on an OpenStack Object Storage server. You need
|
||||
the following information:
|
||||
|
||||
* Username
|
||||
* Bucket
|
||||
* Region
|
||||
* API Key
|
||||
* Tenantname
|
||||
* Password
|
||||
* Service Name
|
||||
* URL of identity Endpoint
|
||||
* Timeout of HTTP request
|
||||
@@ -0,0 +1,7 @@
|
||||
========
|
||||
ownCloud
|
||||
========
|
||||
|
||||
An ownCloud storage is a specialized :doc:`webdav` storage, with optimizations
|
||||
for ownCloud-ownCloud communication. See the :doc:`webdav` documentation for
|
||||
how to configure an ownCloud external storage.
|
||||
11
admin_manual/configuration_files/external_storage/sftp.rst
Normal file
11
admin_manual/configuration_files/external_storage/sftp.rst
Normal file
@@ -0,0 +1,11 @@
|
||||
====
|
||||
SFTP
|
||||
====
|
||||
|
||||
To connect an SFTP server you need:
|
||||
|
||||
* Whatever name you want for your local mountpoint.
|
||||
* The URL of your SFTP server.
|
||||
* SFTP server username and password.
|
||||
* Remote Subfolder, the SFTP directory to mount in ownCloud.
|
||||
* The ownCloud users or groups who are allowed to access the share.
|
||||
36
admin_manual/configuration_files/external_storage/smb.rst
Normal file
36
admin_manual/configuration_files/external_storage/smb.rst
Normal file
@@ -0,0 +1,36 @@
|
||||
========
|
||||
SMB/CIFS
|
||||
========
|
||||
|
||||
You can mount SMB/CIFS file shares on ownCloud servers that run on Linux. This
|
||||
requires ``php5-libsmbclient`` (`installation instructions
|
||||
<https://software.opensuse.org/download.html?project=isv%3AownCloud%3Acommunity%
|
||||
3A8.1&package=php5-libsmbclient>`_). SMB/CIFS file servers include any Windows
|
||||
file share, Samba servers on Linux and other Unix-type operating systems, and
|
||||
NAS appliances.
|
||||
|
||||
You need the following information:
|
||||
|
||||
* Folder name -- Whatever name you want for your local mountpoint.
|
||||
* Host -- The URL of the Samba server.
|
||||
* Username -- The username or domain/username used to login to the Samba server.
|
||||
* Password -- The password to login to the Samba server.
|
||||
* Share -- The share on the Samba server to mount.
|
||||
* Remote Subfolder -- The remote subfolder inside the Samba share to mount
|
||||
(optional, defaults to ``/``). To assign the ownCloud logon username
|
||||
automatically to the subfolder, use ``$user`` instead of a particular
|
||||
subfolder name. And finally, the ownCloud users and groups who get access
|
||||
to the share.
|
||||
|
||||
.. figure:: ../../images/external-storage-smb.png
|
||||
|
||||
SMB/CIFS using OC login
|
||||
-------------------------
|
||||
|
||||
This works the same way as setting up a SMB/CIFS mount, except you can use your
|
||||
ownCloud logins intead of the SMB/CIFS server logins. To make this work, your
|
||||
ownCloud users need the same login and password as on the SMB/CIFS server.
|
||||
|
||||
.. note:: Shares set up with ``SMB/CIFS using OC login`` cannot be shared in
|
||||
ownCloud. If you need to share your SMB/CIFS mount, then use the SMB/CIFS
|
||||
mount without oC login.
|
||||
21
admin_manual/configuration_files/external_storage/webdav.rst
Normal file
21
admin_manual/configuration_files/external_storage/webdav.rst
Normal file
@@ -0,0 +1,21 @@
|
||||
======
|
||||
WebDAV
|
||||
======
|
||||
|
||||
Use these to mount a directory from any WebDAV server, or another
|
||||
ownCloud server.
|
||||
|
||||
* Folder name -- Whatever name you want for your local mountpoint.
|
||||
* URL -- The URL of the WebDAV or ownCloud server.
|
||||
* Username and password for the remote server
|
||||
* Remote Subfolder -- The remote subfolder you want to mount (optional, defaults
|
||||
to ``/``)
|
||||
* Secure ``https://`` - Whether to use ``https://`` to connect to the WebDav
|
||||
server instead of ``http://`` (We always recommend ``https://`` for
|
||||
security)
|
||||
|
||||
.. figure:: ../../images/external-storage-webdav.png
|
||||
|
||||
.. Note:: CPanel users should install `Web Disk
|
||||
<https://documentation.cpanel.net/display/ALD/Web+Disk>`_ to enable WebDAV
|
||||
functionality.
|
||||
@@ -30,16 +30,19 @@ Supported mounts
|
||||
|
||||
ownCloud admins may mount these external storage services and devices:
|
||||
|
||||
* Local
|
||||
* Amazon S3 and S3 compliant
|
||||
* Dropbox
|
||||
* FTP/SFTP
|
||||
* Google Drive
|
||||
* OpenStack Object Storage
|
||||
* SMB/CIFS
|
||||
* SMB/CIFS using OC login
|
||||
* ownCloud
|
||||
* WebDAV
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
external_storage/amazons3
|
||||
external_storage/dropbox
|
||||
external_storage/ftp
|
||||
external_storage/google
|
||||
external_storage/local
|
||||
external_storage/openstack
|
||||
external_storage/owncloud
|
||||
external_storage/sftp
|
||||
external_storage/smb
|
||||
external_storage/webdav
|
||||
|
||||
ownCloud users can be given permission to mount any of these, except local
|
||||
storage.
|
||||
@@ -94,283 +97,6 @@ You might need to setup a cron job that runs ``sudo -u www-data php occ files:sc
|
||||
to trigger a rescan of the user's files periodically (for example every 15 minutes), which includes
|
||||
the mounted external storage.
|
||||
|
||||
Local Storage
|
||||
-------------
|
||||
|
||||
Use this to mount any directory on your ownCloud server that is outside of your
|
||||
ownCloud ``data/`` directory. This directory must be readable and writable by
|
||||
your HTTP server user.
|
||||
|
||||
In the ``Folder name`` field enter the folder name that you want to appear on
|
||||
your ownCloud ``Files`` page.
|
||||
|
||||
In the ``Configuration`` field enter the full filepath of the directory you
|
||||
want to mount.
|
||||
|
||||
In the ``Available for`` field enter the users or groups who have permission to
|
||||
access the mount.
|
||||
|
||||
.. figure:: ../images/external-storage-app-local.png
|
||||
|
||||
Amazon S3
|
||||
---------
|
||||
|
||||
All you need to connect your Amazon S3 buckets to ownCloud is your S3 Access
|
||||
Key, Secret Key, and your bucket name.
|
||||
|
||||
In the ``Folder name`` field enter the folder name that you want to appear on
|
||||
your ownCloud ``Files`` page.
|
||||
|
||||
In the ``Access Key`` field enter your S3 Access Key.
|
||||
|
||||
In the ``Secret Key`` field enter your S3 Secret Key.
|
||||
|
||||
In the ``Bucket`` field enter the name of your S3 bucket you want to share.
|
||||
|
||||
In the ``Available for`` field enter the users or groups who have permission to
|
||||
access your S3 mount.
|
||||
|
||||
The hostname, port, and region of your S3 server are optional; you will need
|
||||
to use these for non-Amazon S3-compatible servers.
|
||||
|
||||
.. figure:: ../images/external-storage-amazons3.png
|
||||
|
||||
Dropbox
|
||||
-------
|
||||
|
||||
Connecting Dropbox is a little more work because you have to create a Dropbox
|
||||
app. Log into the `Dropbox Developers page <http://www.dropbox.com/developers>`_
|
||||
and click ``App Console``:
|
||||
|
||||
.. figure:: ../images/external-storage-dropbox.png
|
||||
|
||||
If you have not already created any Dropbox apps it will ask you to accept
|
||||
their terms and conditions. Then you are presented with the choice to create
|
||||
either a Drop-ins App or a Dropbox API App. Click ``Dropbox API App``, and then
|
||||
check:
|
||||
|
||||
* Files and datastores.
|
||||
* No -- My app needs access to files already on Dropbox.
|
||||
* All file types -- My app needs access to a user's full Dropbox. Only
|
||||
supported via the CoreAPI.
|
||||
|
||||
Then enter whatever name you want for your app.
|
||||
|
||||
.. figure:: ../images/external-storage-dropbox-app.png
|
||||
|
||||
Now click the ``Create App`` button. Under ``Status``, do not click
|
||||
``Development (Apply for production status)`` because that is for apps that you
|
||||
want to release publicly.
|
||||
|
||||
Click ``Enable additional users`` to allow multiple oC users to use your new
|
||||
Dropbox share.
|
||||
|
||||
Note your App key and App secret, which you will enter in the External Storage
|
||||
form on your ownCloud Admin page.
|
||||
|
||||
.. figure:: ../images/external-storage-dropbox-configapp.png
|
||||
|
||||
Your ownCloud configuration requires only the local mount name, the App Key and
|
||||
the App Secret, and which users or groups have access to the share.
|
||||
|
||||
.. figure:: ../images/external-storage-dropbox-oc.png
|
||||
|
||||
You must be logged into Dropbox, and when ownCloud successfully verifies your
|
||||
connection Dropbox will ask for verification to connect to your Dropbox
|
||||
account. Click ``Allow``, and you're done.
|
||||
|
||||
.. figure:: ../images/external-storage-dropbox-allowshare.png
|
||||
|
||||
FTP/FTPS/SFTP
|
||||
-------------
|
||||
|
||||
Connecting to an FTP server requires:
|
||||
|
||||
* Whatever name you want for your local mountpoint.
|
||||
* The URL of your FTP server, and optionally the port number.
|
||||
* FTP server username and password.
|
||||
* Remote Subfolder, the FTP directory to mount in ownCloud. ownCloud defaults to the root
|
||||
directory. When you specify a different directory you must leave off the
|
||||
leading slash. For example, if you want to connect your
|
||||
``public_html/images`` directory, then type it exactly like that.
|
||||
* Choose whether to connect in the clear with ``ftp://``, or to encrypt your
|
||||
FTP session with SSL/TLS over ``ftps://`` (Your FTP server must be
|
||||
configured to support ``ftps://``)
|
||||
* Enter the ownCloud users or groups who are allowed to access the share.
|
||||
|
||||
.. note:: The external storage ``FTP/FTPS/SFTP`` needs the ``allow_url_fopen`` PHP
|
||||
setting to be set to ``1``. When having connection problems make sure that it is
|
||||
not set to ``0`` in your ``php.ini``.
|
||||
|
||||
.. figure:: ../images/external-storage-ftp.png
|
||||
|
||||
SFTP uses SSH rather than SSL, as FTPS does, so your SFTP sessions are always
|
||||
safely tucked inside an SSH tunnel. To connect an SFTP server you need:
|
||||
|
||||
* Whatever name you want for your local mountpoint.
|
||||
* The URL of your SFTP server.
|
||||
* SFTP server username and password.
|
||||
* Remote Subfolder, the SFTP directory to mount in ownCloud.
|
||||
* The ownCloud users or groups who are allowed to access the share.
|
||||
|
||||
Google Drive
|
||||
------------
|
||||
|
||||
All applications that access a Google API must be registered through the
|
||||
`Google Cloud Console <https://console.developers.google.com/>`_. Follow along carefully
|
||||
because the Google interface is a bit of a maze and it's easy to get lost.
|
||||
|
||||
.. note:: Your ownCloud server must have a registered domain name and be
|
||||
accessible over the Internet; Google Drive will not connect to a LAN-only
|
||||
server.
|
||||
|
||||
If you already have a Google account, such as Groups, Drive, or Mail, you can
|
||||
use your existing login to log into the Google Cloud Console. After logging in
|
||||
click the ``Create Project`` button.
|
||||
|
||||
.. figure:: ../images/external-storage-google-drive.png
|
||||
|
||||
Give your project a name, and either accept the default ``Project ID`` or create
|
||||
your own, then click the ``Create`` button.
|
||||
|
||||
.. figure:: ../images/external-storage-google-drive1.png
|
||||
|
||||
The next screen is your ``Project Dashboard``. The Activities screen on the
|
||||
bottom left shows your current status. In the left sidebar click ``APIs
|
||||
& Auth > APIs``, and then click ``Google Apps APIs > Drive API``.
|
||||
|
||||
.. figure:: ../images/external-storage-google-drive2.png
|
||||
|
||||
Before you click ``Enable API`` you might want to click on ``Learn more`` or
|
||||
``Explore this API``. Then click ``Enable API``.
|
||||
|
||||
.. figure:: ../images/external-storage-google-drive3.png
|
||||
|
||||
``Enable API`` takes you to the Drive API dashboard, with tabs for
|
||||
``Overview, Usage, Quota``, and ``Drive UI Integration``. Feel free to
|
||||
explore, and then go to ``APIs & Auth > Credentials``. This screen has two
|
||||
sections: ``0Auth`` and ``Public API Access``.
|
||||
|
||||
.. figure:: ../images/external-storage-google-drive4.png
|
||||
|
||||
|
||||
Click ``0Auth > Create New Client ID``. The next screen that opens is ``Create
|
||||
Client ID``. Check ``Web Application`` and click the ``Configure Consent
|
||||
Screen`` button. You'll see the consent screen the first time you create a
|
||||
mountpoint for your Google Drive in owncloud.
|
||||
|
||||
.. figure:: ../images/external-storage-google-drive5.png
|
||||
|
||||
There are just a few required fields on the Consent Screen form: the email
|
||||
address of your Google account and your app name. The optional fields include
|
||||
your site URL, a link to your logo, and links to your privacy and terms of
|
||||
service policies. Your logo must be a hosted file because there is no upload
|
||||
dialogue. Click ``Save`` when you're finished.
|
||||
|
||||
.. figure:: ../images/external-storage-google-drive6.png
|
||||
|
||||
Now you should be on the ``Edit Client Settings`` screen. The ``Authorized
|
||||
JavaScript Origins`` is your root domain, for example
|
||||
``https://www.example.com``. You need two ``Authorized Redirect URIs``, which
|
||||
must be in the following form::
|
||||
|
||||
https://example.com/owncloud/index.php/settings/personal
|
||||
https://example.com/owncloud/index.php/settings/admin
|
||||
|
||||
Replace ``https://example.com/owncloud/`` with your own ownCloud server URL,
|
||||
then click ``Save``.
|
||||
|
||||
.. figure:: ../images/external-storage-google-drive10.png
|
||||
|
||||
This should take you back to the 0Auth screen, with a summary of your settings
|
||||
and editing buttons. This contains your ``Client ID`` and ``Client Secret``,
|
||||
which you need to set up your ownCloud connection.
|
||||
|
||||
.. figure:: ../images/external-storage-google-drive11.png
|
||||
|
||||
Go to your ``Admin`` page in ownCloud, create your new folder name, enter the
|
||||
Client ID and Client Secret, select your users and groups, and click ``Grant
|
||||
Access``.
|
||||
|
||||
.. figure:: ../images/external-storage-google-drive8.png
|
||||
|
||||
Google will open a dialogue asking for permission to connect to ownCloud. Click
|
||||
``Accept``. When you see the green light confirming a successful connection
|
||||
you're finished.
|
||||
|
||||
SMB/CIFS
|
||||
--------
|
||||
|
||||
You can mount SMB/CIFS file shares on ownCloud servers that run on Linux. This
|
||||
requires ``php5-libsmbclient`` (`installation instructions
|
||||
<https://software.opensuse.org/download.html?project=isv%3AownCloud%3Acommunity%
|
||||
3A8.1&package=php5-libsmbclient>`_). SMB/CIFS file servers include any Windows
|
||||
file share, Samba servers on Linux and other Unix-type operating systems, and
|
||||
NAS appliances.
|
||||
|
||||
You need the following information:
|
||||
|
||||
* Folder name -- Whatever name you want for your local mountpoint.
|
||||
* Host -- The URL of the Samba server.
|
||||
* Username -- The username or domain/username used to login to the Samba server.
|
||||
* Password -- The password to login to the Samba server.
|
||||
* Share -- The share on the Samba server to mount.
|
||||
* Remote Subfolder -- The remote subfolder inside the Samba share to mount
|
||||
(optional, defaults to ``/``). To assign the ownCloud logon username
|
||||
automatically to the subfolder, use ``$user`` instead of a particular
|
||||
subfolder name. And finally, the ownCloud users and groups who get access
|
||||
to the share.
|
||||
|
||||
.. figure:: ../images/external-storage-smb.png
|
||||
|
||||
SMB/CIFS using OC login
|
||||
-------------------------
|
||||
|
||||
This works the same way as setting up a SMB/CIFS mount, except you can use your
|
||||
ownCloud logins intead of the SMB/CIFS server logins. To make this work, your
|
||||
ownCloud users need the same login and password as on the SMB/CIFS server.
|
||||
|
||||
.. note:: Shares set up with ``SMB/CIFS using OC login`` cannot be shared in
|
||||
ownCloud. If you need to share your SMB/CIFS mount, then use the SMB/CIFS
|
||||
mount without oC login.
|
||||
|
||||
ownCloud and WebDAV
|
||||
-------------------
|
||||
|
||||
Use these to mount a directory from any WebDAV server, or another
|
||||
ownCloud server.
|
||||
|
||||
* Folder name -- Whatever name you want for your local mountpoint.
|
||||
* URL -- The URL of the WebDAV or ownCloud server.
|
||||
* Username and password for the remote server
|
||||
* Remote Subfolder -- The remote subfolder you want to mount (optional, defaults
|
||||
to ``/``)
|
||||
* Secure ``https://`` - Whether to use ``https://`` to connect to the WebDav
|
||||
server instead of ``http://`` (We always recommend ``https://`` for
|
||||
security)
|
||||
|
||||
.. figure:: ../images/external-storage-webdav.png
|
||||
|
||||
.. Note:: CPanel users should install `Web Disk
|
||||
<https://documentation.cpanel.net/display/ALD/Web+Disk>`_ to enable WebDAV
|
||||
functionality.
|
||||
|
||||
OpenStack Object Storage
|
||||
------------------------
|
||||
|
||||
Use this to mount a container on an OpenStack Object Storage server. You need
|
||||
the following information:
|
||||
|
||||
* Username
|
||||
* Bucket
|
||||
* Region
|
||||
* API Key
|
||||
* Tenantname
|
||||
* Password
|
||||
* Service Name
|
||||
* URL of identity Endpoint
|
||||
* Timeout of HTTP request
|
||||
|
||||
Configuration File
|
||||
------------------
|
||||
|
||||
|
||||
Reference in New Issue
Block a user