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

Changes for Nextcloud (#34)

Browse Source 
* Changes for Nextcloud

* Changes for Nextcloud

* Update command_line_installation.rst

-oci Enterprise removed

* removed Enterprise

* Changing to nextcloud

* enterprise removed

* Update external_storage_configuration_gui.rst

typo

* Update command_line_installation.rst

Oracle changed

* to nextcloud

* Update linux_installation.rst

* Update linux_installation.rst
This commit is contained in:
Joachim Sokolowski
2016-06-22 14:41:58 +02:00
committed by Morris Jobke
parent 2dfea72fe2
commit 7b27cf8dcd
35 changed files with 556 additions and 304 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
admin_manual/configuration_database/db_conversion.rst
View File

@@ -3,17 +3,16 @@ Converting Database Type
========================
You can convert a SQLite database to a more performing MySQL, MariaDB or
PostgreSQL database with the ownCloud command line tool. SQLite is good for
testing and simple single-user ownCloud servers, but it does not scale for
PostgreSQL database with the Nextcloud command line tool. SQLite is good for
testing and simple single-user Nextcloud servers, but it does not scale for
multiple-user production users.
.. note:: ownCloud Enterprise edition does not support SQLite.
Run the conversion
------------------
First setup the new database, here called "new_db_name".
In ownCloud root folder call
In Nextcloud root folder call
::
@@ -40,12 +39,12 @@ To successfully proceed with the conversion, you must type ``yes`` when prompted
with the question ``Continue with the conversion?``
On success the converter will automatically configure the new database in your
ownCloud config ``config.php``.
Nextcloud config ``config.php``.
Unconvertible Tables
--------------------
If you updated your ownCloud installation there might exist old tables, which
If you updated your Nextcloud installation there might exist old tables, which
are not used anymore. The converter will tell you which ones.
::
@@ -71,4 +70,4 @@ Here is a list of known old tables:
* oc_media_users
* oc_permissions
* oc_queuedtasks
* oc_sharing
* oc_sharing

18
admin_manual/configuration_files/big_file_upload_configuration.rst
View File

@@ -15,7 +15,7 @@ hard limits that cannot be exceeded:
64-bit filesystems have much higher limits; consult the documentation for your
filesystem.
.. note:: The ownCloud sync client is not affected by these upload limits
.. note:: The Nextcloud sync client is not affected by these upload limits
as it is uploading files in smaller chunks.
System Configuration
@@ -31,9 +31,9 @@ System Configuration
Configuring Your Web server
---------------------------
.. note:: ownCloud comes with its own ``owncloud/.htaccess`` file. Because ``php-fpm``
.. note:: Nextcloud comes with its own ``nextcloud/.htaccess`` file. Because ``php-fpm``
can't read PHP settings in ``.htaccess`` these settings must be set in the
``owncloud/.user.ini`` file.
``nextcloud/.user.ini`` file.
Set the following two parameters inside the corresponding php.ini file (see the
**Loaded Configuration File** section of :ref:`label-phpinfo` to find your
@@ -101,11 +101,11 @@ By default, downloads will be limited to 1GB due to ``proxy_buffering`` and ``pr
Configuring PHP
---------------
If you don't want to use the ownCloud ``.htaccess`` or ``.user.ini`` file, you may
If you don't want to use the Nextcloud ``.htaccess`` or ``.user.ini`` file, you may
configure PHP instead. Make sure to comment out any lines ``.htaccess``
pertaining to upload size, if you entered any.
If you are running ownCloud on a 32-bit system, any ``open_basedir`` directive
If you are running Nextcloud on a 32-bit system, any ``open_basedir`` directive
in your ``php.ini`` file needs to be commented out.
Set the following two parameters inside ``php.ini``, using your own desired
@@ -123,7 +123,7 @@ will return memory-related errors:
* ``output_buffering = 0``
Configuring ownCloud
Configuring Nextcloud
--------------------
As an alternative to the ``upload_tmp_dir`` of PHP (e.g. if you don't have access to your
@@ -142,7 +142,7 @@ Configuring upload limits within the GUI
If all prerequisites described in this documentation are in place an admin can change the
upload limits on demand by using the ``File handling`` input box within the administrative
backend of ownCloud.
backend of Nextcloud.
.. figure:: images/admin_filehandling-1.png
@@ -153,10 +153,10 @@ this input box.
To be able to use this input box you need to make sure that:
* your Web server is be able to use the ``.htaccess`` file shipped by ownCloud (Apache only)
* your Web server is be able to use the ``.htaccess`` file shipped by Nextcloud (Apache only)
* the user your Web server is running as has write permissions to the files ``.htaccess`` and ``.user.ini``
:ref:`strong_perms_label` might prevent write access to these files. As an admin you need
to decide between the ability to use the input box and a more secure ownCloud installation
to decide between the ability to use the input box and a more secure Nextcloud installation
where you need to manually modify the upload limits in the ``.htaccess`` and ``.user.ini``
files described above.

10
admin_manual/configuration_files/collaborative_documents_configuration.rst
View File

@@ -1,19 +1,19 @@
Configuring the Collaborative Documents App
===========================================
The Documents application supports editing documents within ownCloud, without the
The Documents application supports editing documents within Nextcloud, without the
need to launch an external application. The Documents app supports these
features:
* Cooperative edit, with multiple users editing files simultaneously.
* Document creation within ownCloud.
* Document creation within Nextcloud.
* Document upload.
* Share and edit files in the browser, and then share them inside ownCloud or
* Share and edit files in the browser, and then share them inside Nextcloud or
through a public link.
Supported file formats are `.odt`, `.doc`, and `.docx`. `.odt` is supported
natively in ownCloud, and you must have LibreOffice or OpenOffice installed on
the ownCloud server to convert `.doc`, and `.docx` documents.
natively in Nextcloud, and you must have LibreOffice or OpenOffice installed on
the Nextcloud server to convert `.doc`, and `.docx` documents.
Enabling the Documents App
--------------------------

4
admin_manual/configuration_files/default_files_configuration.rst
View File

@@ -3,7 +3,7 @@ Providing Default Files
=======================
You may distribute a set of default files and folders to all users by placing
them in the :file:`owncloud/core/skeleton` directory on your ownCloud server.
them in the :file:`nextcloud/core/skeleton` directory on your Nextcloud server.
These files appear only to new users after their initial login, and existing
users will not see files that are added to this directory after their first
login. The files in the :file:`skeleton` directory are copied into the users'
@@ -14,7 +14,7 @@ This screenshot shows a set of photos in the :file:`skeleton` directory.
.. image:: ../images/skeleton-files.png
They appear on the user's ownCloud Files page just like any other files.
They appear on the user's Nextcloud Files page just like any other files.
.. image:: ../images/skeleton-files1.png

114
admin_manual/configuration_files/encryption_configuration.rst
View File

@@ -2,29 +2,29 @@
Encryption Configuration
========================
The primary purpose of the ownCloud server-side encryption is to protect users'
The primary purpose of the Nextcloud server-side encryption is to protect users'
files on remote storage, such as Dropbox and Google Drive, and to do it easily
and seamlessly from within ownCloud.
and seamlessly from within Nextcloud.
In ownCloud 9.0 the server-side encryption separates encryption of local and
In Nextcloud 9.0 the server-side encryption separates encryption of local and
remote storage. This allows you to encrypt remote storage, such as Dropbox and
Google, without having to also encrypt your home storage on your ownCloud
Google, without having to also encrypt your home storage on your Nextcloud
server.
.. note:: Starting with ownCloud 9.0 we support Authenticated Encryption for all
.. note:: Starting with Nextcloud 9.0 we support Authenticated Encryption for all
newly encrypted files. See https://hackerone.com/reports/108082 for more
technical information about the impact.
For maximum security make sure to configure external storage with "Check for
changes: Never". This will let ownCloud ignore new files not added via ownCloud,
changes: Never". This will let Nextcloud ignore new files not added via Nextcloud,
so a malicious external storage administrator could not add new files to the
storage without your knowledge. Of course, this is not wise if your external
storage is subject to legitimate external changes.
ownCloud server-side encryption encrypts files stored on the ownCloud server,
and files on remote storage that is connected to your ownCloud server.
Encryption and decryption are performed on the ownCloud server. All files sent
to remote storage will be encrypted by the ownCloud server, and upon retrieval,
Nextcloud server-side encryption encrypts files stored on the Nextcloud server,
and files on remote storage that is connected to your Nextcloud server.
Encryption and decryption are performed on the Nextcloud server. All files sent
to remote storage will be encrypted by the Nextcloud server, and upon retrieval,
decrypted before serving them to you and anyone you have shared them with.
.. note:: Encrypting files increases their size by roughly 35%, so you must
@@ -32,11 +32,11 @@ decrypted before serving them to you and anyone you have shared them with.
storage quotas. User's quotas are based on the unencrypted file size, and
not the encrypted file size.
When files on external storage are encrypted in ownCloud, you cannot share them
directly from the external storage services, but only through ownCloud sharing
because the key to decrypt the data never leaves the ownCloud server.
When files on external storage are encrypted in Nextcloud, you cannot share them
directly from the external storage services, but only through Nextcloud sharing
because the key to decrypt the data never leaves the Nextcloud server.
ownCloud's server-side encryption generates a strong encryption key, which is
Nextcloud's server-side encryption generates a strong encryption key, which is
unlocked by user's passwords. Your users don't need to track an extra
password, but simply log in as they normally do. It encrypts only the contents
of files, and not filenames and directory structures.
@@ -51,25 +51,25 @@ The encryption keys are stored in the following directories:
system wide external storage
When encryption is enabled, all files are encrypted and decrypted by the
ownCloud application, and stored encrypted on your remote storage.
This protects your data on externally hosted storage. The ownCloud
Nextcloud application, and stored encrypted on your remote storage.
This protects your data on externally hosted storage. The Nextcloud
admin and the storage admin will see only encrypted files when browsing backend
storage.
.. warning:: Encryption keys are stored only on the ownCloud server, eliminating
.. warning:: Encryption keys are stored only on the Nextcloud server, eliminating
exposure of your data to third-party storage providers. The encryption app
does **not** protect your data if your ownCloud server is compromised, and it
does not prevent ownCloud administrators from reading user's files. This
does **not** protect your data if your Nextcloud server is compromised, and it
does not prevent Nextcloud administrators from reading user's files. This
would require client-side encryption, which this app does not provide. If
your ownCloud server is not connected to any external storage services then
your Nextcloud server is not connected to any external storage services then
it is better to use other encryption tools, such as file-level or
whole-disk encryption.
Note also that SSL terminates at or before Apache on the ownCloud server, and
Note also that SSL terminates at or before Apache on the Nextcloud server, and
all files will exist in an unencrypted state between the SSL connection
termination and the ownCloud code that encrypts and decrypts files. This is
termination and the Nextcloud code that encrypts and decrypts files. This is
also potentially exploitable by anyone with administrator access to your
server. Read `How ownCloud uses encryption to protect your data
server. Read `How Nextcloud uses encryption to protect your data
<https://owncloud.org/blog/how-owncloud-uses-encryption-to-protect-your-
data/>`_ for more information.
@@ -77,7 +77,7 @@ Before Enabling Encryption
--------------------------
Plan very carefully before enabling encryption because it is not reversible via
the ownCloud Web interface. If you lose your encryption keys your files are not
the Nextcloud Web interface. If you lose your encryption keys your files are not
recoverable. Always have backups of your encryption keys stored in a safe
location, and consider enabling all recovery options.
@@ -88,10 +88,10 @@ You have more options via the ``occ`` command (see :ref:`occ_encryption_label`)
Enabling Encryption
-------------------
ownCloud encryption consists of two parts. The base encryption system is
Nextcloud encryption consists of two parts. The base encryption system is
enabled and disabled on your Admin page. First you must enable this, and then
select an encryption module to load. Currently the only available encryption
module is the ownCloud Default Encryption Module.
module is the Nextcloud Default Encryption Module.
First go to the **Server-side encryption** section of your Admin page and check
**Enable server-side encryption**. You have one last chance to change your mind.
@@ -100,11 +100,11 @@ First go to the **Server-side encryption** section of your Admin page and check
After clicking the **Enable Encryption** button you see the message "No
encryption module loaded, please load a encryption module in the app menu", so
go to your Apps page to enable the ownCloud Default Encryption Module.
go to your Apps page to enable the Nextcloud Default Encryption Module.
.. figure:: images/encryption1.png
Return to your Admin page to see the ownCloud Default Encryption
Return to your Admin page to see the Nextcloud Default Encryption
Module added to the module selector, and automatically selected. Now you must
log out and then log back in to initialize your encryption keys.
@@ -146,8 +146,8 @@ storage mount, see :ref:`external_storage_mount_options_label`
Enabling Users File Recovery Keys
----------------------------------
If you lose your ownCloud password, then you lose access to your encrypted
files. If one of your users loses their ownCloud password their files are
If you lose your Nextcloud password, then you lose access to your encrypted
files. If one of your users loses their Nextcloud password their files are
unrecoverable. You cannot reset their password in the normal way; you'll see a
yellow banner warning "Please provide an admin recovery password, otherwise all
user data will be lost".
@@ -209,9 +209,9 @@ module is OC_DEFAULT_MODULE)::
The [module ID] is taken from the ``encryption:list-modules`` command.
Encrypt all data files for all users. For performance reasons, when you enable
encryption on an ownCloud server only new and changed files are encrypted. This
encryption on an Nextcloud server only new and changed files are encrypted. This
command gives you the option to encrypt all files. You must first put your
ownCloud server into single-user mode to prevent any user activity until
Nextcloud server into single-user mode to prevent any user activity until
encryption is completed::
occ maintenance:singleuser
@@ -221,7 +221,7 @@ Then run ``occ``::
occ encryption:encrypt-all
You are about to start to encrypt all files stored in your ownCloud.
You are about to start to encrypt all files stored in your Nextcloud.
It will depend on the encryption module you use which files get encrypted.
Depending on the number and size of your files this can take some time.
Please make sure that no users access their files during this process!
@@ -264,7 +264,7 @@ Disabling Encryption
--------------------
You may disable encryption only with ``occ``. Make sure you have backups of all
encryption keys, including users'. Put your ownCloud server into
encryption keys, including users'. Put your Nextcloud server into
single-user mode, and then disable your encryption module with this command::
occ maintenance:singleuser --on
@@ -296,50 +296,8 @@ LDAP and Other External User Back-ends
If you use an external user back-end, such as an LDAP or Samba server, and you
change a user's password on the back-end, the user will be prompted to change
their ownCloud login to match on their next ownCloud login. The user will need
their Nextcloud login to match on their next Nextcloud login. The user will need
both their old and new passwords to do this. If you have enabled the Recovery
Key then you can change a user's password in the ownCloud Users panel to match
Key then you can change a user's password in the Nextcloud Users panel to match
their back-end password, and then, of course, notify the user and give them
their new password.
.. _upgrading_encryption_label:
Encryption migration to ownCloud 8.0
------------------------------------
When you upgrade from older versions of ownCloud to ownCloud 8.0, you must manually migrate
your encryption keys with the *occ* command after the upgrade is complete, like this
example for CentOS: *sudo -u apache php occ encryption:migrate-keys* You must run *occ* as
your HTTP user. See :doc:`../configuration_server/occ_command` to learn more about *occ*.
Encryption migration to ownCloud 8.1
------------------------------------
The encryption backend has changed in ownCloud 8.1 again, so you must take some
additional steps to migrate encryption correctly. If you do not follow these
steps you may not be able to access your files.
Before you start your upgrade, put your ownCloud server into
``maintenance:singleuser`` mode (See :doc:`../maintenance/enable_maintenance`.)
You must do this to prevent users and sync clients from accessing files before
you have completed your encryption migration.
After your upgrade is complete, follow the steps in
:ref:`enable_encryption_label` to
enable the new encryption system. Then click the **Start Migration** button on
your Admin page to migrate your encryption keys, or use the ``occ`` command. We
strongly recommend using the ``occ`` command; the **Start Migration** button is
for admins who do not have access to the console, for example installations on
shared hosting. This example is for Debian/Ubuntu Linux::
$ sudo -u www-data php occ encryption:migrate
This example is for Red Hat/CentOS/Fedora Linux::
$ sudo -u apache php occ encryption:migrate
You must run ``occ`` as your HTTP user; see
:doc:`../configuration_server/occ_command`.
When you are finished, take your ownCloud server out of
``maintenance:singleuser`` mode.

2
admin_manual/configuration_files/external_storage/amazons3.rst
View File

@@ -2,7 +2,7 @@
Amazon S3
=========
To connect your Amazon S3 buckets to ownCloud, you will need:
To connect your Amazon S3 buckets to Nextcloud, you will need:
- S3 access key
- S3 secret key

10
admin_manual/configuration_files/external_storage/auth_mechanisms.rst
View File

@@ -2,7 +2,7 @@
External Storage Authentication mechanisms
==========================================
ownCloud storage backends accept one or more authentication schemes such as
Nextcloud storage backends accept one or more authentication schemes such as
passwords, OAuth, or token-based, to name a few examples. Each authentication
scheme may be implemented by multiple authentication mechanisms. Different
mechanisms require different configuration parameters, depending on their
@@ -25,18 +25,18 @@ Password-based Mechanisms
The **Username and password** mechanism requires a manually-defined username and
password. These get passed directly to the backend.
The **Log-in credentials, save in session** mechanism uses the ownCloud login
The **Log-in credentials, save in session** mechanism uses the Nextcloud login
credentials of the user to connect to the storage. These are not stored anywhere
on the server, but rather in the user session, giving increased security. The
drawbacks are that sharing is disabled when this mechanism is in use, as
ownCloud has no access to the storage credentials, and background file scanning
Nextcloud has no access to the storage credentials, and background file scanning
does not work.
Public-key Mechanisms
---------------------
Currently only the RSA mechanism is implemented, where a public/private
keypair is generated by ownCloud and the public half shown in the GUI. The keys
keypair is generated by Nextcloud and the public half shown in the GUI. The keys
are generated in the SSH format, and are currently 1024 bits in length. Keys
can be regenerated with a button in the GUI.
@@ -49,7 +49,7 @@ OAuth
OAuth 1.0 and OAuth 2.0 are both implemented, but currently limited to the
Dropbox and Google Drive backends respectively. These mechanisms require
additional configuration at the service provider, where an app ID and app
secret are provided and then entered into ownCloud. Then ownCloud can
secret are provided and then entered into Nextcloud. Then Nextcloud can
perform an authentication request, establishing the storage connection.
.. figure:: images/dropbox-oc.png

8
admin_manual/configuration_files/external_storage/dropbox.rst
View File

@@ -2,7 +2,7 @@
Dropbox
=======
While Dropbox supports the newer OAuth 2.0, ownCloud uses OAuth 1.0, so you can
While Dropbox supports the newer OAuth 2.0, Nextcloud uses OAuth 1.0, so you can
safely ignore any references to OAuth 2.0 in the Dropbox configuration.
Connecting Dropbox is a little more work because you have to create a Dropbox
@@ -37,10 +37,10 @@ that you want to release publicly.
.. figure:: images/dropbox-4.png
:alt: Your app's page.
Click **Enable additional users** to allow multiple ownCloud users to access
Click **Enable additional users** to allow multiple Nextcloud users to access
your new Dropbox share.
Now go to your ownCloud Admin page. Your ownCloud configuration requires only
Now go to your Nextcloud Admin page. Your Nextcloud configuration requires only
the local mount name, the **App Key** and the **App Secret**, and which users
or groups have access to the share. Remember the little gear icon at the
far right for additional options.
@@ -49,7 +49,7 @@ After entering your local mount name, **App Key** and **App Secret**, click
**Grant access**.
.. figure:: images/dropbox-6.png
:alt: ownCloud Dropbox configuration.
:alt: Nextcloud Dropbox configuration.
If you are not already logged into Dropbox, you will be prompted to login
and authorize access. This happens only once, when you are first creating

6
admin_manual/configuration_files/external_storage/ftp.rst
View File

@@ -9,19 +9,19 @@ To connect to an FTP server, you will need:
* The URL of the FTP server
* Port number (default: 21)
* FTP server username and password
* Remote Subfolder, the FTP directory to mount in ownCloud. ownCloud defaults
* Remote Subfolder, the FTP directory to mount in Nextcloud. Nextcloud defaults
to the root directory. If you specify a subfolder you must leave
off the leading slash. For example, ``public_html/images``
Your new mountpoint is available to all users by default, and you may restrict
access by entering specific users or groups in the **Available for** field.
Optionally, ownCloud can use FTPS (FTP over SSL) by checking **Secure ftps://**.
Optionally, Nextcloud can use FTPS (FTP over SSL) by checking **Secure ftps://**.
This requires additional configuration with your root certificate if the FTP
server uses a self-signed certificate.
.. figure:: images/ftp.png
:alt: ownCloud GUI FTP configuration.
:alt: Nextcloud GUI FTP configuration.
.. 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

18
admin_manual/configuration_files/external_storage/google.rst
View File

@@ -2,8 +2,8 @@
Google Drive
============
ownCloud uses OAuth 2.0 to connect to Google Drive. This requires configuration
through Google to get an app ID and app secret, as ownCloud registers itself
Nextcloud uses OAuth 2.0 to connect to Google Drive. This requires configuration
through Google to get an app ID and app secret, as Nextcloud registers itself
as an app.
All applications that access a Google API must be registered through the
@@ -56,7 +56,7 @@ will use 0Auth 2.0.
:alt: Another warning to create credentials.
Now we have to create a consent screen. This is the information in the screen
Google shows you when you connect your new Google app to ownCloud the first
Google shows you when you connect your new Google app to Nextcloud the first
time. Click **Configure consent screen**. Then fill in the required form fields.
Your logo must be hosted, as you cannot upload it, so enter its URL. When
you're finished click **Save**.
@@ -69,10 +69,10 @@ then enter your app name. **Authorized JavaScript Origins** is your root domain,
for example ``https://example.com``, without a trailing slash. You need two
**Authorized Redirect URIs**, and they must be in this form::
https://example.com/owncloud/index.php/settings/personal
https://example.com/owncloud/index.php/settings/admin
https://example.com/nextcloud/index.php/settings/personal
https://example.com/nextcloud/index.php/settings/admin
Replace ``https://example.com/owncloud/`` with your own ownCloud server URL,
Replace ``https://example.com/nextcloud/`` with your own Nextcloud server URL,
then click **Create**.
.. figure:: images/google-drive9.png
@@ -90,11 +90,11 @@ to see complete information.
.. figure:: images/google-drive11.png
:alt: Client ID and client secret
Now you have everything you need to mount your Google Drive in ownCloud.
Now you have everything you need to mount your Google Drive in Nextcloud.
Go to the External Storage section of your Admin page, create your new folder
name, enter the Client ID and Client Secret, and click **Grant Access**. Your
consent page appears when ownCloud makes a successful connection. Click
consent page appears when Nextcloud makes a successful connection. Click
**Allow**.
.. figure:: images/google-drive12.png
@@ -104,7 +104,7 @@ When you see the green light confirming a successful connection
you're finished.
.. figure:: images/google-drive13.png
:alt: Google Drive mount in ownCloud.
:alt: Google Drive mount in Nextcloud.
See :doc:`../external_storage_configuration_gui` for additional mount
options and information.

10
admin_manual/configuration_files/external_storage/local.rst
View File

@@ -2,13 +2,13 @@
Local
=====
Local storages provide access to any directory on the ownCloud server. Since
Local storages provide access to any directory on the Nextcloud server. Since
this is a significant security risk, Local storage can only be configured in
the ownCloud admin settings. Non-admin users cannot create Local storage
the Nextcloud admin settings. Non-admin users cannot create Local storage
mounts.
Use this to mount any directory on your ownCloud server that is outside
of your ownCloud ``data/`` directory. This directory must be readable and
Use this to mount any directory on your Nextcloud server that is outside
of your Nextcloud ``data/`` directory. This directory must be readable and
writable by your HTTP server user. These ownership and permission examples
are on Ubuntu Linux::
@@ -19,7 +19,7 @@ See :ref:`strong_perms_label` for information on correct file permissions, and
find your HTTP user :ref:`label-phpinfo`.
In the **Folder name** field enter the folder name that you want to appear on
your ownCloud Files page.
your Nextcloud Files page.
In the **Configuration** field enter the full filepath of the directory you
want to mount.

2
admin_manual/configuration_files/external_storage/openstack.rst
View File

@@ -8,7 +8,7 @@ OpenStack mechanism, and the other is used exclusively for Rackspace, a provider
of object storage that uses the OpenStack Swift protocol.
The OpenStack authentication mechanism uses the OpenStack Keystone v2
protocol. Your ownCloud configuration needs:
protocol. Your Nextcloud configuration needs:
* **Bucket**. This is user-defined; think of it as a subdirectory of your total
storage. The bucket will be created if it does not exist.

18
admin_manual/configuration_files/external_storage/owncloud.rst
View File

@@ -1,15 +1,15 @@
========
ownCloud
========
=========
Nextcloud
=========
An ownCloud storage is a specialized :doc:`webdav` storage, with optimizations
for ownCloud-ownCloud communication. See the :doc:`webdav` documentation to
learn how to configure an ownCloud external storage.
An Nextcloud storage is a specialized :doc:`webdav` storage, with optimizations
for Nextcloud-Nextcloud communication. See the :doc:`webdav` documentation to
learn how to configure an Nextcloud external storage.
When filling in the **URL** field, use the path to the root of the ownCloud
When filling in the **URL** field, use the path to the root of the Nextcloud
installation, rather than the path to the WebDAV endpoint. So, for a server at
``https://example.com/owncloud``, use ``https://example.com/owncloud`` and not
``https://example.com/owncloud/remote.php/dav``.
``https://example.com/nextcloud``, use ``https://example.com/nextcloud`` and not
``https://example.com/nextcloud/remote.php/dav``.
See :doc:`../external_storage_configuration_gui` for additional mount
options and information.

4
admin_manual/configuration_files/external_storage/sftp.rst
View File

@@ -2,7 +2,7 @@
SFTP
====
ownCloud's SFTP (FTP over an SSH tunne) backend supports both password and
Nextcloud's SFTP (FTP over an SSH tunne) backend supports both password and
public key authentication.
The **Host** field is required; a port can be specified as part of the **Host**
@@ -16,7 +16,7 @@ your **SFTP with secret key login** configuration.
:alt: Generating an RSA key pair in the SFTP configuration.
After generating your keys, you need to copy your new public key to the
destination server to ``.ssh/authorized_keys``. ownCloud will then use its
destination server to ``.ssh/authorized_keys``. Nextcloud will then use its
private key to authenticate to the SFTP server.
The default **Remote Subfolder** is the root directory (``/``) of the remote

14
admin_manual/configuration_files/external_storage/smb.rst
View File

@@ -2,11 +2,11 @@
SMB/CIFS
========
ownCloud can connect to Windows file servers or other SMB-compatible servers
Nextcloud can connect to Windows file servers or other SMB-compatible servers
with the SMB/CIFS backend.
.. note:: The SMB/CIFS backend requires ``smbclient`` or
the PHP smbclient module to be installed on the ownCloud server. The PHP
the PHP smbclient module to be installed on the Nextcloud server. The PHP
smbclient module is preferred, but either will work. These
should be included in any Linux distribution. (See `PECL smbclient
<https://pecl.php.net/package/smbclient>`_ if your distro does not include
@@ -21,10 +21,10 @@ You need the following information:
* 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
(optional, defaults to /). To assign the Nextcloud 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.
* And finally, the Nextcloud users and groups who get access to the share.
Optionally, you can specify a ``Domain``. This is useful in
cases where the
@@ -35,10 +35,8 @@ modified. This is concatenated with the username, so the backend gets
.. note:: For improved reliability and performance, we recommended installing
``libsmbclient-php``, a native PHP module for connecting to
SMB servers. It is available as ``php5-libsmbclient`` in the ownCloud
`OBS repositories <https://download.owncloud.org/download/repositories/
stable/owncloud/>`_
SMB servers.
.. figure:: images/smb.png
:alt: Samba external storage configuration.
:scale: 75%

4
admin_manual/configuration_files/external_storage/webdav.rst
View File

@@ -3,12 +3,12 @@ WebDAV
======
Use this backend to mount a directory from any WebDAV server, or another
ownCloud server.
Nextcloud server.
You need the following information:
* Folder name: The name of your local mountpoint.
* The URL of the WebDAV or ownCloud server.
* The URL of the WebDAV or Nextcloud server.
* Username and password for the remote server
* Secure https://: We always recommend https:// for security, though you can
leave this unchecked for http://.

2
admin_manual/configuration_files/external_storage_configuration.rst
View File

@@ -2,6 +2,6 @@
Configuring External Storage (Configuration File)
=================================================
Starting with ownCloud 9.0, the :file:`data/mount.json` file for configuring
Starting with Nextcloud 9.0, the :file:`data/mount.json` file for configuring
external storages has been removed, and replaced with a set of
:ref:`occ commands <files_external_label>`.

19
admin_manual/configuration_files/external_storage_configuration_gui.rst
View File

@@ -3,12 +3,12 @@ Configuring External Storage (GUI)
==================================
The External Storage Support application enables you to mount external storage
services and devices as secondary ownCloud storage devices. You may also allow
services and devices as secondary Nextcloud storage devices. You may also allow
users to mount their own external storage services.
ownCloud 9.0 introduces a new set of :ref:`occ commands for managing external storage <files_external_label>`.
Nextcloud 9.0 introduces a new set of :ref:`occ commands for managing external storage <files_external_label>`.
Also new in 9.0 is an option for the ownCloud admin to enable or disable sharing
Also new in 9.0 is an option for the Nextcloud admin to enable or disable sharing
on individual external mountpoints (see
:ref:`external_storage_mount_options_label`). Sharing on such mountpoints is
disabled by default.
@@ -49,7 +49,7 @@ public key**.
Required fields are marked with a red border. When all required fields are
filled, the storage is automatically saved. A green dot next to the storage row
indicates the storage is ready for use. A red or yellow icon indicates
that ownCloud could not connect to the external storage, so you need to
that Nextcloud could not connect to the external storage, so you need to
re-check your configuration and network availability.
If there is an error on the storage, it will be marked as unavailable for ten
@@ -83,7 +83,7 @@ individually with the following options:
The **Encryption** checkbox is visible only when the Encryption app is enabled.
**Enable Sharing** allows the ownCloud admin to enable or disable sharing on individual mountpoints.
**Enable Sharing** allows the Nextcloud admin to enable or disable sharing on individual mountpoints.
When sharing is disabled the shares are retained internally, so that you can re-enable sharing
and the previous shares become available again. Sharing is disabled by default.
@@ -95,7 +95,7 @@ Using Self-Signed Certificates
When using self-signed certificates for external storage mounts the certificate
must be imported into the personal settings of the user. Please refer to
`ownCloud HTTPS External Mount
`Nextcloud HTTPS External Mount
<http://ownclouden.blogspot.de/2014/11/owncloud-https-external-mount.html>`_
for more information.
@@ -113,6 +113,7 @@ may provide their own backends, which are not listed here.
external_storage/ftp
external_storage/google
external_storage/local
external_storage/nextcloud
external_storage/openstack
external_storage/owncloud
external_storage/sftp
@@ -138,11 +139,11 @@ Adding Files to External Storages
We recommend configuring the background job **Webcron** or
**Cron** (see :doc:`../configuration_server/background_jobs_configuration`)
to enable ownCloud to automatically detect files added to your external
to enable Nextcloud to automatically detect files added to your external
storages.
ownCloud may not always be able to find out what has been
changed remotely (files changed without going through ownCloud), especially
Nextcloud may not always be able to find out what has been
changed remotely (files changed without going through Nextcloud), especially
when it's very deep in the folder hierarchy of the external storage.
You might need to setup a cron job that runs ``sudo -u www-data php occ files:scan --all``

36
admin_manual/configuration_files/federated_cloud_sharing_configuration.rst
View File

@@ -4,8 +4,8 @@ Configuring Federation Sharing
Federated Cloud Sharing is now managed by the Federation app (9.0+), and is
now called Federation sharing. When you enable the Federation app you can
easily and securely link file shares between ownCloud servers, in effect
creating a cloud of ownClouds.
easily and securely link file shares between Nextcloud servers, in effect
creating a cloud of Nextclouds.
Sharing With ownCloud 8 and Older
---------------------------------
@@ -19,13 +19,13 @@ ownCloud 8 and older, so you must create Federation shares with public links
Creating a new Federation Share (9.0+ only)
-------------------------------------------
Follow these steps to create a new Federation share between two ownCloud 9.0+
Follow these steps to create a new Federation share between two Nextcloud 9.0+
servers. This requires no action by the user on the remote server; all it takes
is a few steps on the originating server.
1. Enable the Federation app.
2. Go to your ownCloud Admin page and scroll to the Sharing
2. Go to your Nextcloud Admin page and scroll to the Sharing
section. Verify that **Allow users on this server to send shares to other
servers** and **Allow users on this server to receive shares from other
servers** are enabled.
@@ -33,16 +33,16 @@ is a few steps on the originating server.
3. Now go to the Federation
section. By default, **Add server automatically once a federated share was
created successfully** is checked. The Federation app supports creating a
list of trusted ownCloud servers, which allows the trusted servers to
list of trusted Nextcloud servers, which allows the trusted servers to
exchange user directories and auto-complete the names of external users when
you create shares. If you do not want this enabled, then un-check it.
.. figure:: images/federation-0.png
3. Now go to your Files page and select a folder to share. Click the share
icon, and then enter the username and URL of the user on the remote ownCloud
server. In this example, that is ``freda@https://example.com/owncloud``.
When ownCloud verifies the link, it displays it with the **(remote)** label.
icon, and then enter the username and URL of the user on the remote Nextcloud
server. In this example, that is ``freda@https://example.com/nextcloud``.
When Nextcloud verifies the link, it displays it with the **(remote)** label.
Click on this label to establish the link.
.. figure:: images/federation-2.png
@@ -54,16 +54,16 @@ is a few steps on the originating server.
You may disconnect the share at any time by clicking the trash can icon.
Configuring Trusted ownCloud Servers
Configuring Trusted Nextcloud Servers
------------------------------------
You may create a list of trusted ownCloud servers for Federation sharing. This
allows your linked ownCloud servers to share user directories, and to auto-fill
You may create a list of trusted Nextcloud servers for Federation sharing. This
allows your linked Nextcloud servers to share user directories, and to auto-fill
user names in share dialogs. If **Add server automatically once a federated
share was created successfully** is enabled on your Admin page, servers will be
automatically added to your trusted list when you create new Federation shares.
You may also enter ownCloud server URLs in the **Add ownCloud Server** field.
You may also enter Nextcloud server URLs in the **Add Nextcloud Server** field.
The yellow light indicates a successful connection, with no user names
exchanged. The green light indicates a successful connection with user names
exchanged. A red light means the connection failed.
@@ -80,7 +80,7 @@ ownCloud 8.x and older.
Check the ``Share Link`` checkbox to expose more sharing options (which are
described more fully in :doc:`file_sharing_configuration`). You may create a
Federation share by allowing ownCloud to create a public link for you, and then
Federation share by allowing Nextcloud to create a public link for you, and then
email it to the person you want to create the share with.
.. figure:: images/create_public_share-6.png
@@ -88,12 +88,12 @@ email it to the person you want to create the share with.
You may optionally set a password and expiration date on it. When your recipient
receives your email they must click the link, or copy it to a Web
browser. They will see a page displaying a thumbnail of the file, with a button
to **Add to your ownCloud**.
to **Add to your Nextcloud**.
.. figure:: images/create_public_share-8.png
Your recipient should click the **Add to your ownCloud** button. On the next
screen your recipient needs to enter the URL to their ownCloud
Your recipient should click the **Add to your Nextcloud** button. On the next
screen your recipient needs to enter the URL to their Nextcloud
server, and then press the return key.
.. figure:: images/create_public_share-9.png
@@ -122,11 +122,11 @@ Your Apache Web server must have ``mod_rewrite`` enabled, and you must have
connections (see :doc:`../installation/installation_wizard`). Consider also
enabling SSL to encrypt all traffic between your servers .
Your ownCloud server creates the share link from the URL that you used to log
Your Nextcloud server creates the share link from the URL that you used to log
into the server, so make sure that you log into your server using a URL that is
accessible to your users. For example, if you log in via its LAN IP address,
such as ``http://192.168.10.50``, then your share URL will be something like
``http://192.168.10.50/owncloud/index.php/s/jWfCfTVztGlWTJe``, which is not
``http://192.168.10.50/nextcloud/index.php/s/jWfCfTVztGlWTJe``, which is not
accessible outside of your LAN. This also applies to using the server name; for
access outside of your LAN you need to use a fully-qualified domain name such as
``http://myserver.example.com``, rather than ``http://myserver``.

22
admin_manual/configuration_files/file_sharing_configuration.rst
View File

@@ -2,9 +2,9 @@
File Sharing
============
ownCloud users can share files with their ownCloud groups and other users on
the same ownCloud server, with ownCloud users on :doc:`other ownCloud servers <federated_cloud_sharing_configuration>`, and create public shares for people who are not
ownCloud users. You have control of a number of user permissions on file shares:
Nextcloud users can share files with their Nextcloud groups and other users on
the same Nextcloud server, with Nextcloud users on :doc:`other Nextcloud servers <federated_cloud_sharing_configuration>`, and create public shares for people who are not
Nextcloud users. You have control of a number of user permissions on file shares:
* Allow users to share files
* Allow users to create public shares
@@ -16,7 +16,7 @@ ownCloud users. You have control of a number of user permissions on file shares:
* Allow email notifications of new public shares
* Exclude groups from creating shares
.. note:: ownCloud Enterprise includes a Share Link Password Policy app; see
.. note:: Nextcloud includes a Share Link Password Policy app; see
:ref:`password_policy_label`.
Configure your sharing policy on your Admin page in the Sharing section.
@@ -26,13 +26,13 @@ Configure your sharing policy on your Admin page in the Sharing section.
* Check ``Allow apps to use the Share API`` to enable users to share files. If
this is not checked, no users can create file shares.
* Check ``Allow users to share via link`` to enable creating public shares for
people who are not ownCloud users via hyperlink.
people who are not Nextcloud users via hyperlink.
* Check ``Enforce password protection`` to force users to set a password on all
public share links. This does not apply to local user and group shares.
* Check ``Allow public uploads`` to allow anyone to upload files to
public shares.
* Check ``Allow users to send mail notification for shared files`` to enable
sending notifications from ownCloud. (Your ownCloud server must be configured
sending notifications from Nextcloud. (Your Nextcloud server must be configured
to send mail)
* Check ``Set default expiration date`` to set a default expiration date on
public shares.
@@ -47,16 +47,16 @@ Configure your sharing policy on your Admin page in the Sharing section.
(including the one they are on) via a remote share.
* Check ``Allow users to send mail notification for shared files`` enables
users to send an email notification to every ownCloud user that the file is
users to send an email notification to every Nextcloud user that the file is
shared with.
* Check ``Exclude groups from sharing`` to prevent members of specific groups
from creating any file shares in those groups. When you check this, you'll
get a dropdown list of all your groups to choose from. Members of excluded
groups can still receive shares, but not create any
* Check ``Allow username autocompletion in share dialog`` to enable
auto-completion of ownCloud usernames.
auto-completion of Nextcloud usernames.
.. note:: ownCloud does not preserve the mtime (modification time) of
.. note:: Nextcloud does not preserve the mtime (modification time) of
directories, though it does update the mtimes on files. See
`Wrong folder date when syncing
<https://github.com/owncloud/core/issues/7009>`_ for discussion of this.
@@ -82,7 +82,7 @@ Creating Persistent File Shares
When a user is deleted, their files are also deleted. As you can imagine, this
is a problem if they created file shares that need to be preserved, because
these disappear as well. In ownCloud files are tied to their owners, so
these disappear as well. In Nextcloud files are tied to their owners, so
whatever happens to the file owner also happens to the files.
One solution is to create persistent shares for your users. You can retain
@@ -99,7 +99,7 @@ edits them.
Share Link Password Policy
--------------------------
ownCloud Enterprise users have the option of enabling the Share Link Password
Nextcloud users have the option of enabling the Share Link Password
Policy app. This allows you to enforce password length, required characters,
define special characters, and expiration dates on share links.

14
admin_manual/configuration_files/file_versioning.rst
View File

@@ -7,18 +7,18 @@ ensure that users don't exceed their storage quotas. This is the default
pattern used to delete old versions:
* For the first second we keep one version
* For the first 10 seconds ownCloud keeps one version every 2 seconds
* For the first minute ownCloud keeps one version every 10 seconds
* For the first hour ownCloud keeps one version every minute
* For the first 24 hours ownCloud keeps one version every hour
* For the first 30 days ownCloud keeps one version every day
* After the first 30 days ownCloud keeps one version every week
* For the first 10 seconds Nextcloud keeps one version every 2 seconds
* For the first minute Nextcloud keeps one version every 10 seconds
* For the first hour Nextcloud keeps one version every minute
* For the first 24 hours Nextcloud keeps one version every hour
* For the first 30 days Nextcloud keeps one version every day
* After the first 30 days Nextcloud keeps one version every week
The versions are adjusted along this pattern every time a new version is
created.
The Versions app never uses more that 50% of the user's currently available
free space. If the stored versions exceed this limit, ownCloud deletes the
free space. If the stored versions exceed this limit, Nextcloud deletes the
oldest file versions until it meets the disk space limit again.
You may alter the default pattern in ``config.php``. The default setting is

12
admin_manual/configuration_files/files_locking_transactional.rst
View File

@@ -2,7 +2,7 @@
Transactional File Locking
==========================
ownCloud's Transactional File Locking mechanism locks files to avoid
Nextcloud's Transactional File Locking mechanism locks files to avoid
file corruption during normal operation. It performs these functions:
* Operates at a higher level than the filesystem, so you don't need to use a
@@ -24,15 +24,15 @@ document, or give notice that other users are working on the same document.
Multiple users can open and edit a file at the same time and Transactional File
locking does not prevent this. Rather, it prevents simultaneous file saving.
.. note:: Transactional file locking is in ownCloud core, and replaces the old
File Locking app. The File Locking app has been removed from ownCloud in
version 8.2.1. If your ownCloud server still has the File Locking app, you
.. note:: Transactional file locking is in Nextcloud core, and replaces the old
File Locking app. The File Locking app has been removed from Nextcloud in
version 8.2.1. If your Nextcloud server still has the File Locking app, you
must visit your Apps page to verify that it is disabled; the File Locking
app and Transactional File Locking cannot both operate at the same time.
File locking is enabled by default, using the database locking backend. This
places a significant load on your database. Using ``memcache.locking`` relieves
the database load and improves performance. Admins of ownCloud servers with
the database load and improves performance. Admins of Nextcloud servers with
heavy workloads should install a memcache. (See
:doc:`../configuration_server/caching_configuration`.)
@@ -53,7 +53,7 @@ configuration in your ``config.php`` file like this example::
a password. See http://redis.io/topics/security for more information.
If you want to configure Redis to listen on an Unix socket (which is
recommended if Redis is running on the same system as ownCloud) use this example
recommended if Redis is running on the same system as Nextcloud) use this example
``config.php`` configuration::
'filelocking.enabled' => true,

10
admin_manual/configuration_files/previews_configuration.rst
View File

@@ -2,15 +2,15 @@
Previews Configuration
======================
The ownCloud thumbnail system generates previews of files for all
ownCloud apps that display files, such as Files and Gallery.
The Nextcloud thumbnail system generates previews of files for all
Nextcloud apps that display files, such as Files and Gallery.
The following image shows some examples of previews of various file types.
.. figure:: ../images/preview_images.png
:alt: Thumbnails of various image and audio/video files.
By default, ownCloud can generate previews for the following filetypes:
By default, Nextcloud can generate previews for the following filetypes:
* Images files
* Cover of MP3 files
@@ -26,7 +26,7 @@ By default, ownCloud can generate previews for the following filetypes:
Parameters
----------
Please notice that the ownCloud preview system comes already with sensible
Please notice that the Nextcloud preview system comes already with sensible
defaults, and therefore it is usually unnecessary to adjust those configuration
values.
@@ -72,7 +72,7 @@ to a maximum size of 100×100px:
Maximum scale factor:
~~~~~~~~~~~~~~~~~~~~~
If a lot of small pictures are stored on the ownCloud instance and the preview
If a lot of small pictures are stored on the Nextcloud instance and the preview
system generates blurry previews, you might want to consider setting a maximum
scale factor. By default, pictures are upscaled to 10 times the original size:

24
admin_manual/installation/command_line_installation.rst
View File

@@ -1,13 +1,13 @@
=========================================
Installing ownCloud From the Command Line
Installing Nextcloud from the Command Line
=========================================
It is now possible to install ownCloud entirely from the command line. This is
It is now possible to install Nextcloud entirely from the command line. This is
convenient for scripted operations, headless servers, and sysadmins who prefer
the command line. There are three stages to installing ownCloud via the command
the command line. There are three stages to installing Nextcloud via the command
line:
1. Download and install the ownCloud code via your package manager, or download
1. Download and install the Nextcloud code via your package manager, or download
and unpack the tarball in the appropriate directories. (See
:doc:`linux_installation` and :doc:`source_installation`.)
@@ -24,31 +24,31 @@ of running the graphical Installation Wizard::
$ sudo -u www-data php occ maintenance:install --database
"mysql" --database-name "nextcloud" --database-user "root" --database-pass
"password" --admin-user "admin" --admin-pass "password"
ownCloud is not installed - only a limited number of commands are available
ownCloud was successfully installed
Nextcloud is not installed - only a limited number of commands are available
Nextcloud was successfully installed
Note that you must change to the root ownCloud directory, as in the example
Note that you must change to the root Nextcloud directory, as in the example
above, to run ``occ maintenance:install``, or the installation will fail with
a PHP fatal error message.
Supported databases are::
- sqlite (SQLite3 - ownCloud Community edition only)
- sqlite (SQLite3 - Nextcloud Community edition only)
- mysql (MySQL/MariaDB)
- pgsql (PostgreSQL)
- oci (Oracle - ownCloud Enterprise edition only)
- oci (Oracle 11g currently only possible if you contact us at https://nextcloud.com/enterprise as part of a subscription)
See :ref:`command_line_installation_label` for more information.
Finally, apply the correct strong permissions to your ownCloud files and
Finally, apply the correct strong permissions to your Nextcloud files and
directories (see :ref:`strong_perms_label`). This is an extremely important
step. It helps protect your ownCloud installation, and ensures that it will run
step. It helps protect your Nextcloud installation, and ensures that it will run
correctly.
BINLOG_FORMAT = STATEMENT
-------------------------
If your ownCloud installation fails and you see this in your ownCloud log::
If your Nextcloud installation fails and you see this in your Nextcloud log::
An unhandled exception has been thrown: exception ‘PDOException’ with message
'SQLSTATE[HY000]: General error: 1665 Cannot execute statement: impossible to

12
admin_manual/installation/deployment_recommendations.rst
View File

@@ -79,7 +79,7 @@ Authentication via an existing LDAP or Active Directory server.
scale the DB.
* Backup
Install owncloud, Nextcloud data directory and database on Btrfs filesystem.
Install Nextcloud, Nextcloud data directory and database on Btrfs filesystem.
Make regular snapshots at desired intervals for zero downtime backups.
Mount DB partitions with the "nodatacow" option to prevent fragmentation.
@@ -482,19 +482,19 @@ References
.. _Maintenance:
https://doc.owncloud.org/server/9.0/admin_manual/maintenance/index.html
https://docs.nextcloud.org/server/9/admin_manual/maintenance/index.html
.. _User Authentication with LDAP:
https://doc.owncloud.org/server/9.0/admin_manual/configuration_user/
https://docs.nextcloud.org/server/9/admin_manual/configuration_user/
user_auth_ldap.html
.. _Configuring Memory Caching:
https://doc.owncloud.org/server/9.0/admin_manual/configuration_server/
https://docs.nextcloud.org/server/9/admin_manual/configuration_server/
caching_configuration.html
.. _Nextcloud Server or Enterprise Edition:
https://owncloud.com/owncloud-server-or-enterprise-edition/
https://nextcloud.com/enterprise/
.. _F5 Big-IP: https://f5.com/products/big-ip/
.. _Shibboleth Integration:
https://doc.owncloud.org/server/9.0/admin_manual/enterprise_user_management/
https://docs.nextcloud.org/server/9/admin_manual/enterprise_user_management/
user_auth_shibboleth.html
.. _Memcache StorageService:
https://wiki.shibboleth.net/confluence/display/SHIB2/

2
admin_manual/installation/index.rst
View File

@@ -19,4 +19,4 @@ Installation
selinux_configuration
nginx_examples
nginx_owncloud_8x
nginx_owncloud_9x
nginx_nextcloud_9x

57
admin_manual/installation/installation_wizard.rst
View File

@@ -5,7 +5,7 @@ Installation Wizard
Quick Start
-----------
When ownCloud prerequisites are fulfilled and all ownCloud files are installed,
When Nextcloud prerequisites are fulfilled and all Nextcloud files are installed,
the last step to completing the installation is running the Installation
Wizard.
This is just three steps:
@@ -18,9 +18,9 @@ This is just three steps:
:scale: 75%
:alt: screenshot of the installation wizard
You're finished and can start using your new ownCloud server.
You're finished and can start using your new Nextcloud server.
Of course, there is much more that you can do to set up your ownCloud server for
Of course, there is much more that you can do to set up your Nextcloud server for
best performance and security. In the following sections we will cover important
installation and post-installation steps. Note that you must follow the
instructions in :ref:`Setting Strong Permissions <strong_perms_label>` in order
@@ -37,15 +37,15 @@ Data Directory Location
-----------------------
Click **Storage and Database** to expose additional installation configuration
options for your ownCloud data directory and database.
options for your Nextcloud data directory and database.
.. figure:: images/install-wizard-a1.png
:scale: 75%
:alt: installation wizard with all options exposed
You should locate your ownCloud data directory outside of your Web root if you
You should locate your Nextcloud data directory outside of your Web root if you
are using an HTTP server other than Apache, or you may wish to store your
ownCloud data in a different location for other reasons (e.g. on a storage
Nextcloud data in a different location for other reasons (e.g. on a storage
server). It is best to configure your data directory location at installation,
as it is difficult to move after installation. You may put it anywhere; in this
example is it located in ``/var/oc_data``. This directory must already exist,
@@ -57,33 +57,32 @@ and must be owned by your HTTP user (see
Database Choice
---------------
SQLite is the default database for ownCloud Server (it is not available and not supported
in the ownCloud Enterprise edition), and it is good only for testing and lightweight single-user
setups without client synchronization. Supported databases are MySQL, MariaDB,
Oracle 11g (ownCloud Enterprise edition only), and PostgreSQL, and we recommend
:doc:`MySQL/MariaDB <system_requirements>`. Your database and PHP connectors
must be installed before you run the Installation Wizard. When you install
ownCloud from packages all the necessary dependencies will be satisfied (see
:doc:`source_installation` for a detailed listing of required and optional PHP
modules). You will need the root database login, or any administrator login that
has permissions to create and modify databases, and then enter any name you want
for your ownCloud database.
SQLite is the default database for Nextcloud Server and it is good only for
testing and lightweight single-user setups without client synchronization.
Supported databases are MySQL, MariaDB, Oracle 11g , and PostgreSQL, and we
recommend :doc:`MySQL/MariaDB <system_requirements>`. Your database and PHP
connectors must be installed before you run the Installation Wizard. When
you install Nextcloud from packages all the necessary dependencies will be
satisfied (see :doc:`source_installation` for a detailed listing of required
and optional PHP modules). You will need the root database login, or any
administrator login that has permissions to create and modify databases, and
then enter any name you want for your Nextcloud database.
After you enter your root or administrator login for your database, the
installer creates a special database user with privileges limited to the
ownCloud database. Then ownCloud needs only the special ownCloud database
user, and drops the root dB login. This user is named for your ownCloud admin
user, with an ``oc_`` prefix, and then given a random password. The ownCloud
Nextcloud database. Then Nextcloud needs only the special Nextcloud database
user, and drops the root dB login. This user is named for your Nextcloud admin
user, with an ``oc_`` prefix, and then given a random password. The Nextcloud
database user and password are written into ``config.php``::
'dbuser' => 'oc_molly',
'dbpassword' => 'pX65Ty5DrHQkYPE5HRsDvyFHlZZHcm',
Click Finish Setup, and start using your new ownCloud server.
Click Finish Setup, and start using your new Nextcloud server.
.. figure:: images/install-wizard-a2.png
:scale: 75%
:alt: ownCloud welcome screen after a successful installation
:alt: Nextcloud welcome screen after a successful installation
Now we will look at some important post-installation steps.
@@ -92,9 +91,9 @@ Now we will look at some important post-installation steps.
Trusted Domains
---------------
All URLs used to access your ownCloud server must be whitelisted in your
All URLs used to access your Nextcloud server must be whitelisted in your
``config.php`` file, under the ``trusted_domains`` setting. Users
are allowed to log into ownCloud only when they point their browsers to a
are allowed to log into Nextcloud only when they point their browsers to a
URL that is listed in the ``trusted_domains`` setting. You may use IP addresses
and domain names. A typical configuration looks like this::
@@ -137,12 +136,12 @@ use :ref:`label-phpinfo` (Look for the **User/Group** line).
.. note:: When using an NFS mount for the data directory, do not change its
ownership from the default. The simple act of mounting the drive will set
proper permissions for ownCloud to write to the directory. Changing
proper permissions for Nextcloud to write to the directory. Changing
ownership as above could result in some issues if the NFS mount is
lost.
The easy way to set the correct permissions is to copy and run this script.
Replace the ``ocpath`` variable with the path to your ownCloud directory, and
Replace the ``ocpath`` variable with the path to your Nextcloud directory, and
replace the ``htuser`` and ``htgroup`` variables with your HTTP user and group::
#!/bin/bash
@@ -183,10 +182,10 @@ replace the ``htuser`` and ``htgroup`` variables with your HTTP user and group::
chown ${rootuser}:${htgroup} ${ocpath}/data/.htaccess
fi
If you have customized your ownCloud installation and your filepaths are
If you have customized your Nextcloud installation and your filepaths are
different than the standard installation, then modify this script accordingly.
This lists the recommended modes and ownership for your ownCloud directories
This lists the recommended modes and ownership for your Nextcloud directories
and files:
* All files should be read-write for the file owner, read-only for the
@@ -204,6 +203,6 @@ and files:
* Both :file:`.htaccess` files are read-write file owner, read-only group and
world
These strong permissions prevent upgrading your ownCloud server;
These strong permissions prevent upgrading your Nextcloud server;
see :ref:`set_updating_permissions_label` for a script to quickly change
permissions to allow upgrading.

8
admin_manual/installation/linux_installation.rst
View File

@@ -2,6 +2,14 @@
Preferred Linux Installation Method
===================================
Nextcloud
---------
Nextcloud Linux distribution packages are not available at the moment (June 2016)!
The following Text reffers to the OwnCloud packages
Changes in 9.0
--------------

26
admin_manual/installation/nginx_examples.rst
View File

@@ -2,14 +2,14 @@
Nginx Example Configurations
============================
This page covers example Nginx configurations to use with running an ownCloud
This page covers example Nginx configurations to use with running an Nextcloud
server. Note that Nginx is not officially supported, and this page is
community-maintained. (Thank you, contributors!)
- You need to insert the following code into **your Nginx configuration file.**
- The configuration assumes that ownCloud is installed in
``/var/www/owncloud`` and that it is accessed via
- The configuration assumes that Nextcloud is installed in
``/var/www/nextcloud`` and that it is accessed via
``http(s)://cloud.example.com``.
- Adjust **server_name**, **root**, **ssl_certificate** and
**ssl_certificate_key** to suit your needs.
@@ -27,9 +27,9 @@ Example Configurations
----------------------
- :doc:`nginx_owncloud_8x`
- :doc:`nginx_owncloud_9x`
- :doc:`nginx_nextcloud_9x`
You can use ownCloud over plain http, but we strongly encourage you to use
You can use Nextcloud over plain http, but we strongly encourage you to use
SSL/TLS to encrypt all of your server traffic, and to protect user's logins and
data in transit.
@@ -91,10 +91,10 @@ To use http_v2 for nginx you have to check two things:
2.) When you have used SPDY before, the nginx config has to be changed from
``listen 443 ssl spdy;`` to ``listen 443 ssl http2;``
nginx: caching ownCloud gallery thumbnails
nginx: caching Nextcloud gallery thumbnails
==========================================
One of the optimizations for ownCloud when using nginx as the Web server is to
One of the optimizations for Nextcloud when using nginx as the Web server is to
combine FastCGI caching with "Cache Purge", a `3rdparty nginx module
<http://wiki.nginx.org/3rdPartyModules>`_ that adds the ability to purge
content from `FastCGI`, `proxy`, `SCGI` and `uWSGI` caches. This mechanism
@@ -109,7 +109,7 @@ adapt it according your OS type and release.
Unlike Apache, nginx does not dynamically load modules. All modules needed
must be compiled into nginx. This is one of the reasons for nginx´s
performance. It is expected to have an already running nginx installation
with a working configuration set up as described in the ownCloud
with a working configuration set up as described in the Nextcloud
documentation.
nginx module check
@@ -246,12 +246,12 @@ Configure nginx with the ``nginx-cache-purge`` module
::
sudo vi /etc/nginx/sites-enabled/{your-ownCloud-nginx-config-file}
sudo vi /etc/nginx/sites-enabled/{your-nextcloud-nginx-config-file}
Add at the *beginning*, but *outside* the ``server{}`` block::
# cache_purge
fastcgi_cache_path {path} levels=1:2 keys_zone=OWNCLOUD:100m inactive=60m;
fastcgi_cache_path {path} levels=1:2 keys_zone=NEXTCLOUD:100m inactive=60m;
map $request_uri $skip_cache {
default 1;
~*/thumbnail.php 0;
@@ -260,7 +260,7 @@ Add at the *beginning*, but *outside* the ``server{}`` block::
}
.. note:: Please adopt or delete any regex line in the ``map`` block according
your needs and the ownCloud version used.
your needs and the Nextcloud version used.
As an alternative to mapping, you can use as many ``if`` statements in
your server block as necessary::
@@ -289,7 +289,7 @@ Add *inside* the ``server{}`` block, as an example of a configuration::
# cache_purge
fastcgi_cache_bypass $skip_cache;
fastcgi_no_cache $skip_cache;
fastcgi_cache OWNCLOUD;
fastcgi_cache NEXTCLOUD;
fastcgi_cache_valid 60m;
fastcgi_cache_methods GET HEAD;
}
@@ -312,7 +312,7 @@ Add *inside* the ``server{}`` block, as an example of a configuration::
sudo nginx -s reload
* Open your browser and clear your cache.
* Logon to your ownCloud instance, open the gallery app, move through your
* Logon to your Nextcloud instance, open the gallery app, move through your
folders and watch while the thumbnails are generated for the first time.
* You may also watch with eg. ``htop`` your system load while the
thumbnails are processed.

289
admin_manual/installation/nginx_nextcloud_9x.rst Normal file
View File

@@ -0,0 +1,289 @@
=================================================
Nginx Configuration for the Nextcloud 9.x Branches
=================================================
The following configuration should be used when Nextcloud is placed in the
webroot of your Nginx installation. Be careful about line breaks if you copy
the examples, as long lines may be broken for page formatting.
Some environments might need a ``cgi.fix_pathinfo`` set to ``1`` in their
``php.ini``.
Thanks to `@josh4trunks <https://github.com/josh4trunks>`_ for providing /
creating these configuration examples.
Nextcloud in the webroot of nginx
--------------------------------
The following config should be used when Nextcloud is placed in the webroot of
your nginx installation.
::
upstream php-handler {
server 127.0.0.1:9000;
#server unix:/var/run/php5-fpm.sock;
}
server {
listen 80;
server_name cloud.example.com;
# enforce https
return 301 https://$server_name$request_uri;
}
server {
listen 443 ssl;
server_name cloud.example.com;
ssl_certificate /etc/ssl/nginx/cloud.example.com.crt;
ssl_certificate_key /etc/ssl/nginx/cloud.example.com.key;
# Add headers to serve security related headers
# Before enabling Strict-Transport-Security headers please read into this
# topic first.
# add_header Strict-Transport-Security "max-age=15768000;
# includeSubDomains; preload;";
add_header X-Content-Type-Options nosniff;
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block";
add_header X-Robots-Tag none;
add_header X-Download-Options noopen;
add_header X-Permitted-Cross-Domain-Policies none;
# Path to the root of your installation
root /var/www/nextcloud/;
location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}
# The following 2 rules are only needed for the user_webfinger app.
# Uncomment it if you're planning to use this app.
#rewrite ^/.well-known/host-meta /public.php?service=host-meta last;
#rewrite ^/.well-known/host-meta.json /public.php?service=host-meta-json
# last;
location = /.well-known/carddav { return 301
$scheme://$host/remote.php/dav; }
location = /.well-known/caldav { return 301
$scheme://$host/remote.php/dav; }
location /.well-known/acme-challenge { }
# set max upload size
client_max_body_size 512M;
fastcgi_buffers 64 4K;
# Disable gzip to avoid the removal of the ETag header
gzip off;
# Uncomment if your server is build with the ngx_pagespeed module
# This module is currently not supported.
#pagespeed off;
error_page 403 /core/templates/403.php;
error_page 404 /core/templates/404.php;
location / {
rewrite ^ /index.php$uri;
}
location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)/ {
deny all;
}
location ~ ^/(?:\.|autotest|occ|issue|indie|db_|console) {
deny all;
}
location ~
^/(?:index|remote|public|cron|core/ajax/update|status|ocs/v[12]|updater
/.+|ocs-provider/.+|core/templates/40[34])\.php(?:$|/) {
include fastcgi_params;
fastcgi_split_path_info ^(.+\.php)(/.+)$;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_param PATH_INFO $fastcgi_path_info;
fastcgi_param HTTPS on;
#Avoid sending the security headers twice
fastcgi_param modHeadersAvailable true;
fastcgi_param front_controller_active true;
fastcgi_pass php-handler;
fastcgi_intercept_errors on;
fastcgi_request_buffering off;
}
location ~ ^/(?:updater|ocs-provider)(?:$|/) {
try_files $uri/ =404;
index index.php;
}
# Adding the cache control header for js and css files
# Make sure it is BELOW the PHP block
location ~* \.(?:css|js)$ {
try_files $uri /index.php$uri$is_args$args;
add_header Cache-Control "public, max-age=7200";
# Add headers to serve security related headers (It is intended to
# have those duplicated to the ones above)
# Before enabling Strict-Transport-Security headers please read into
# this topic first.
# add_header Strict-Transport-Security "max-age=15768000;
# includeSubDomains; preload;";
add_header X-Content-Type-Options nosniff;
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block";
add_header X-Robots-Tag none;
add_header X-Download-Options noopen;
add_header X-Permitted-Cross-Domain-Policies none;
# Optional: Don't log access to assets
access_log off;
}
location ~* \.(?:svg|gif|png|html|ttf|woff|ico|jpg|jpeg)$ {
try_files $uri /index.php$uri$is_args$args;
# Optional: Don't log access to other assets
access_log off;
}
}
Nextcloud in a subdir of nginx
------------------------------
The following config should be used when Nextcloud is placed within a subdir of
your nginx installation.
::
upstream php-handler {
server 127.0.0.1:9000;
#server unix:/var/run/php5-fpm.sock;
}
server {
listen 80;
server_name cloud.example.com;
# enforce https
return 301 https://$server_name$request_uri;
}
server {
listen 443 ssl;
server_name cloud.example.com;
ssl_certificate /etc/ssl/nginx/cloud.example.com.crt;
ssl_certificate_key /etc/ssl/nginx/cloud.example.com.key;
# Add headers to serve security related headers
# Before enabling Strict-Transport-Security headers please read into this
# topic first.
#add_header Strict-Transport-Security "max-age=15768000;
# includeSubDomains; preload;";
add_header X-Content-Type-Options nosniff;
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block";
add_header X-Robots-Tag none;
add_header X-Download-Options noopen;
add_header X-Permitted-Cross-Domain-Policies none;
# Path to the root of your installation
root /var/www/;
location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}
# The following 2 rules are only needed for the user_webfinger app.
# Uncomment it if you're planning to use this app.
# rewrite ^/.well-known/host-meta /nextcloud/public.php?service=host-meta
# last;
#rewrite ^/.well-known/host-meta.json
# /nextcloud/public.php?service=host-meta-json last;
location = /.well-known/carddav { return 301
$scheme://$host/nextcloud/remote.php/dav; }
location = /.well-known/caldav { return 301
$scheme://$host/nextcloud/remote.php/dav; }
location /.well-known/acme-challenge { }
location ^~ /nextcloud {
# set max upload size
client_max_body_size 512M;
fastcgi_buffers 64 4K;
# Disable gzip to avoid the removal of the ETag header
gzip off;
# Uncomment if your server is build with the ngx_pagespeed module
# This module is currently not supported.
#pagespeed off;
error_page 403 /nextcloud/core/templates/403.php;
error_page 404 /nextcloud/core/templates/404.php;
location /nextcloud {
rewrite ^ /nextcloud/index.php$uri;
}
location ~
^/nextcloud/(?:build|tests|config|lib|3rdparty|templates|data)/ {
deny all;
}
location ~ ^/nextcloud/(?:\.|autotest|occ|issue|indie|db_|console) {
deny all;
}
location ~
^/nextcloud/(?:index|remote|public|cron|core/ajax/update|status|ocs/v[12]|
updater/.+|ocs-provider/.+|core/templates/40[34])\.php(?:$|/) {
include fastcgi_params;
fastcgi_split_path_info ^(.+\.php)(/.+)$;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_param PATH_INFO $fastcgi_path_info;
fastcgi_param HTTPS on;
#Avoid sending the security headers twice
fastcgi_param modHeadersAvailable true;
fastcgi_param front_controller_active true;
fastcgi_pass php-handler;
fastcgi_intercept_errors on;
fastcgi_request_buffering off;
}
location ~ ^/nextcloud/(?:updater|ocs-provider)(?:$|/) {
try_files $uri/ =404;
index index.php;
}
# Adding the cache control header for js and css files
# Make sure it is BELOW the PHP block
location ~* \.(?:css|js)$ {
try_files $uri /nextcloud/index.php$uri$is_args$args;
add_header Cache-Control "public, max-age=7200";
# Add headers to serve security related headers (It is intended
# to have those duplicated to the ones above)
# Before enabling Strict-Transport-Security headers please read
# into this topic first.
# add_header Strict-Transport-Security "max-age=15768000;
# includeSubDomains; preload;";
add_header X-Content-Type-Options nosniff;
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block";
add_header X-Robots-Tag none;
add_header X-Download-Options noopen;
add_header X-Permitted-Cross-Domain-Policies none;
# Optional: Don't log access to assets
access_log off;
}
location ~* \.(?:svg|gif|png|html|ttf|woff|ico|jpg|jpeg)$ {
try_files $uri /nextcloud/index.php$uri$is_args$args;
# Optional: Don't log access to other assets
access_log off;
}
}
}

44
admin_manual/installation/nginx_owncloud_9x.rst
View File

@@ -1,8 +1,8 @@
=================================================
Nginx Configuration for the ownCloud 9.x Branches
Nginx Configuration for the Nextcloud 9.x Branches
=================================================
The following configuration should be used when ownCloud is placed in the
The following configuration should be used when Nextcloud is placed in the
webroot of your Nginx installation. Be careful about line breaks if you copy
the examples, as long lines may be broken for page formatting.
@@ -12,10 +12,10 @@ Some environments might need a ``cgi.fix_pathinfo`` set to ``1`` in their
Thanks to `@josh4trunks <https://github.com/josh4trunks>`_ for providing /
creating these configuration examples.
ownCloud in the webroot of nginx
Nextcloud in the webroot of nginx
--------------------------------
The following config should be used when ownCloud is placed in the webroot of
The following config should be used when Nextcloud is placed in the webroot of
your nginx installation.
::
@@ -52,7 +52,7 @@ your nginx installation.
add_header X-Permitted-Cross-Domain-Policies none;
# Path to the root of your installation
root /var/www/owncloud/;
root /var/www/nextcloud/;
location = /robots.txt {
allow all;
@@ -147,10 +147,10 @@ your nginx installation.
}
}
ownCloud in a subdir of nginx
Nextcloud in a subdir of nginx
------------------------------
The following config should be used when ownCloud is placed within a subdir of
The following config should be used when Nextcloud is placed within a subdir of
your nginx installation.
::
@@ -197,19 +197,19 @@ your nginx installation.
# The following 2 rules are only needed for the user_webfinger app.
# Uncomment it if you're planning to use this app.
# rewrite ^/.well-known/host-meta /owncloud/public.php?service=host-meta
# rewrite ^/.well-known/host-meta /nextcloud/public.php?service=host-meta
# last;
#rewrite ^/.well-known/host-meta.json
# /owncloud/public.php?service=host-meta-json last;
# /nextcloud/public.php?service=host-meta-json last;
location = /.well-known/carddav { return 301
$scheme://$host/owncloud/remote.php/dav; }
$scheme://$host/nextcloud/remote.php/dav; }
location = /.well-known/caldav { return 301
$scheme://$host/owncloud/remote.php/dav; }
$scheme://$host/nextcloud/remote.php/dav; }
location /.well-known/acme-challenge { }
location ^~ /owncloud {
location ^~ /nextcloud {
# set max upload size
client_max_body_size 512M;
@@ -222,23 +222,23 @@ your nginx installation.
# This module is currently not supported.
#pagespeed off;
error_page 403 /owncloud/core/templates/403.php;
error_page 404 /owncloud/core/templates/404.php;
error_page 403 /nextcloud/core/templates/403.php;
error_page 404 /nextcloud/core/templates/404.php;
location /owncloud {
rewrite ^ /owncloud/index.php$uri;
location /nextcloud {
rewrite ^ /nextcloud/index.php$uri;
}
location ~
^/owncloud/(?:build|tests|config|lib|3rdparty|templates|data)/ {
^/nextcloud/(?:build|tests|config|lib|3rdparty|templates|data)/ {
deny all;
}
location ~ ^/owncloud/(?:\.|autotest|occ|issue|indie|db_|console) {
location ~ ^/nextcloud/(?:\.|autotest|occ|issue|indie|db_|console) {
deny all;
}
location ~
^/owncloud/(?:index|remote|public|cron|core/ajax/update|status|ocs/v[12]|
^/nextcloud/(?:index|remote|public|cron|core/ajax/update|status|ocs/v[12]|
updater/.+|ocs-provider/.+|core/templates/40[34])\.php(?:$|/) {
include fastcgi_params;
fastcgi_split_path_info ^(.+\.php)(/.+)$;
@@ -253,7 +253,7 @@ your nginx installation.
fastcgi_request_buffering off;
}
location ~ ^/owncloud/(?:updater|ocs-provider)(?:$|/) {
location ~ ^/nextcloud/(?:updater|ocs-provider)(?:$|/) {
try_files $uri/ =404;
index index.php;
}
@@ -261,7 +261,7 @@ your nginx installation.
# Adding the cache control header for js and css files
# Make sure it is BELOW the PHP block
location ~* \.(?:css|js)$ {
try_files $uri /owncloud/index.php$uri$is_args$args;
try_files $uri /nextcloud/index.php$uri$is_args$args;
add_header Cache-Control "public, max-age=7200";
# Add headers to serve security related headers (It is intended
# to have those duplicated to the ones above)
@@ -280,7 +280,7 @@ your nginx installation.
}
location ~* \.(?:svg|gif|png|html|ttf|woff|ico|jpg|jpeg)$ {
try_files $uri /owncloud/index.php$uri$is_args$args;
try_files $uri /nextcloud/index.php$uri$is_args$args;
# Optional: Don't log access to other assets
access_log off;
}

2
admin_manual/installation/php_54_installation.rst
View File

@@ -2,7 +2,7 @@
Installing PHP 5.4 on RHEL 6 and CentOS 6
=========================================
Red Hat Enterprise Linux and CentOS 6 still ship with PHP 5.3. ownCloud
Red Hat Enterprise Linux and CentOS 6 still ship with PHP 5.3. Nextcloud
requires PHP 5.4 or better. There are several third-party repositories that
supply PHP 5.4, but you must use the Software Collections (SCL) repository to
be in compliance with your RHEL support contract, and not any other third-party

6
admin_manual/installation/php_55_installation.rst
View File

@@ -2,7 +2,7 @@
Installing PHP 5.5 on RHEL 7 and CentOS 7
=========================================
PHP 5.4 has been end-of-life since September 2015 and is no longer supported by the PHP team. RHEL 7 still ships with PHP 5.4, and Red Hat supports it. ownCloud also supports PHP 5.4, so upgrading is not required. However, it is highly recommended to upgrade to PHP 5.5+ for best security and performance.
PHP 5.4 has been end-of-life since September 2015 and is no longer supported by the PHP team. RHEL 7 still ships with PHP 5.4, and Red Hat supports it. Nextcloud also supports PHP 5.4, so upgrading is not required. However, it is highly recommended to upgrade to PHP 5.5+ for best security and performance.
**Before upgrading, evaluate all of your PHP apps for compatibility with PHP 5.5.**
@@ -21,7 +21,7 @@ You must also install the updated database module for your database. This instal
yum install php55-php-mysqlnd
If you are using the ownCloud LDAP app, you need this module::
If you are using the Nextcloud LDAP app, you need this module::
yum install php55-php-ldap
@@ -63,7 +63,7 @@ You must also install the updated database module for your database. This instal
yum install php55-php-mysqlnd
If you are using the ownCloud LDAP app, you need this module::
If you are using the Nextcloud LDAP app, you need this module::
yum install php55-php-ldap

12
admin_manual/installation/selinux_configuration.rst
View File

@@ -5,8 +5,8 @@ SELinux Configuration
=====================
When you have SELinux enabled on your Linux distribution, you may run into
permissions problems after a new ownCloud installation, and see ``permission
denied`` errors in your ownCloud logs.
permissions problems after a new Nextcloud installation, and see ``permission
denied`` errors in your Nextcloud logs.
The following settings should work for most SELinux systems that use the
default distro profiles. Run these commands as root, and remember to adjust the filepaths
@@ -19,8 +19,8 @@ in these examples for your installation::
semanage fcontext -a -t httpd_sys_rw_content_t '/var/www/html/nextcloud/apps'
restorecon '/var/www/html/nextcloud/apps'
If you uninstall ownCloud you need to remove the ownCloud directory labels. To do
this execute the following commands as root after uninstalling ownCloud::
If you uninstall Nextcloud you need to remove the Nextcloud directory labels. To do
this execute the following commands as root after uninstalling Nextcloud::
semanage fcontext -d -t httpd_sys_rw_content_t '/var/www/html/nextcloud/data'
restorecon '/var/www/html/nextcloud/data'
@@ -53,7 +53,7 @@ Use this setting to allow LDAP connections::
Allow access to remote network
------------------------------
ownCloud requires access to remote networks for functions such as Server-to-Server sharing, external storages or
Nextcloud requires access to remote networks for functions such as Server-to-Server sharing, external storages or
the app store. To allow this access use the following setting::
setsebool -P httpd_can_network_connect on
@@ -61,7 +61,7 @@ the app store. To allow this access use the following setting::
Allow access to SMTP/sendmail
-----------------------------
If you want to allow ownCloud to send out e-mail notifications via sendmail you need
If you want to allow Nextcloud to send out e-mail notifications via sendmail you need
to use the following setting::
setsebool -P httpd_can_sendmail on

8
admin_manual/installation/system_requirements.rst
View File

@@ -5,11 +5,11 @@ System Requirements
Memory
------
Memory requirements for running an ownCloud server are greatly variable,
Memory requirements for running an Nextcloud server are greatly variable,
depending on the numbers of users and files, and volume of server activity.
ownCloud needs a minimum of 128MB RAM, and we recommend a minimum of 512MB.
Nextcloud needs a minimum of 128MB RAM, and we recommend a minimum of 512MB.
Recommended Setup for Running ownCloud
Recommended Setup for Running Nextcloud
--------------------------------------
For best performance, stability, support, and full functionality we recommend:
@@ -38,4 +38,4 @@ Supported Platforms
Safari 5+
See :doc:`source_installation` for minimum software versions for installing
ownCloud.
Nextcloud.