mirror of
https://github.com/nextcloud/documentation.git
synced 2026-01-02 17:59:36 +07:00
changed more ownCloud references to Nextcloud
This commit is contained in:
Patric Lenhart
@@ -1,16 +1,16 @@
|
||||
Automatic Configuration Setup
|
||||
=============================
|
||||
|
||||
If you need to install ownCloud on multiple servers, you normally do not want
|
||||
If you need to install Nextcloud on multiple servers, you normally do not want
|
||||
to set up each instance separately as described in
|
||||
:doc:`../configuration_database/linux_database_configuration`.
|
||||
For this reason, ownCloud provides an automatic configuration feature.
|
||||
For this reason, Nextcloud provides an automatic configuration feature.
|
||||
|
||||
To take advantage of this feature, you must create a configuration file, called
|
||||
:file:`../owncloud/config/autoconfig.php`, and set the file parameters as required.
|
||||
You can specify any number of parameters in this file. Any unspecified parameters appear on the "Finish setup" screen when you first launch ownCloud.
|
||||
:file:`../nextcloud/config/autoconfig.php`, and set the file parameters as required.
|
||||
You can specify any number of parameters in this file. Any unspecified parameters appear on the "Finish setup" screen when you first launch Nextcloud.
|
||||
|
||||
The :file:`../owncloud/config/autoconfig.php` is automatically removed after the initial configuration has been applied.
|
||||
The :file:`../nextcloud/config/autoconfig.php` is automatically removed after the initial configuration has been applied.
|
||||
|
||||
Parameters
|
||||
----------
|
||||
@@ -37,7 +37,7 @@ Using the following parameter settings, the "Finish setup" screen requests datab
|
||||
|
||||
<?php
|
||||
$AUTOCONFIG = array(
|
||||
"directory" => "/www/htdocs/owncloud/data",
|
||||
"directory" => "/www/htdocs/nextcloud/data",
|
||||
);
|
||||
|
||||
|
||||
@@ -50,7 +50,7 @@ Using the following parameter settings, the "Finish setup" screen requests data
|
||||
<?php
|
||||
$AUTOCONFIG = array(
|
||||
"dbtype" => "sqlite",
|
||||
"dbname" => "owncloud",
|
||||
"dbname" => "nextcloud",
|
||||
"dbtableprefix" => "",
|
||||
);
|
||||
|
||||
@@ -63,7 +63,7 @@ Using the following parameter settings, the "Finish setup" screen requests data
|
||||
<?php
|
||||
$AUTOCONFIG = array(
|
||||
"dbtype" => "mysql",
|
||||
"dbname" => "owncloud",
|
||||
"dbname" => "nextcloud",
|
||||
"dbuser" => "username",
|
||||
"dbpass" => "password",
|
||||
"dbhost" => "localhost",
|
||||
@@ -83,7 +83,7 @@ Using the following parameter settings, the "Finish setup" screen requests data
|
||||
<?php
|
||||
$AUTOCONFIG = array(
|
||||
"dbtype" => "pgsql",
|
||||
"dbname" => "owncloud",
|
||||
"dbname" => "nextcloud",
|
||||
"dbuser" => "username",
|
||||
"dbpass" => "password",
|
||||
"dbhost" => "localhost",
|
||||
@@ -97,21 +97,21 @@ Using the following parameter settings, the "Finish setup" screen requests data
|
||||
All Parameters
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
Using the following parameter settings, because all parameters are already configured in the file, the ownCloud installation skips the "Finish setup" screen.
|
||||
Using the following parameter settings, because all parameters are already configured in the file, the Nextcloud installation skips the "Finish setup" screen.
|
||||
|
||||
::
|
||||
|
||||
<?php
|
||||
$AUTOCONFIG = array(
|
||||
"dbtype" => "mysql",
|
||||
"dbname" => "owncloud",
|
||||
"dbname" => "nextcloud",
|
||||
"dbuser" => "username",
|
||||
"dbpass" => "password",
|
||||
"dbhost" => "localhost",
|
||||
"dbtableprefix" => "",
|
||||
"adminlogin" => "root",
|
||||
"adminpass" => "root-password",
|
||||
"directory" => "/www/htdocs/owncloud/data",
|
||||
"directory" => "/www/htdocs/nextcloud/data",
|
||||
);
|
||||
|
||||
.. note:: Keep in mind that the automatic configuration does not eliminate the need for
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
Defining Background Jobs
|
||||
========================
|
||||
A system like ownCloud sometimes requires tasks to be done on a regular basis without the need for user interaction or hindering ownCloud performance. For that purpose, as a system administrator, you can define background jobs (for example, database clean-ups) which are executed without any need for user interaction.
|
||||
A system like Nextcloud sometimes requires tasks to be done on a regular basis without the need for user interaction or hindering Nextcloud performance. For that purpose, as a system administrator, you can define background jobs (for example, database clean-ups) which are executed without any need for user interaction.
|
||||
|
||||
These jobs are typically referred to as *cron jobs*. Cron jobs are commands or shell-based scripts that are scheduled to run periodically at fixed times, dates, or intervals. ``cron.php`` is an ownCloud internal process that runs such background jobs on demand.
|
||||
These jobs are typically referred to as *cron jobs*. Cron jobs are commands or shell-based scripts that are scheduled to run periodically at fixed times, dates, or intervals. ``cron.php`` is an Nextcloud internal process that runs such background jobs on demand.
|
||||
|
||||
ownCloud plug-in applications register actions with ``cron.php`` automatically to take care of typical housekeeping operations, such as garbage collecting of temporary files or checking for newly updated files using ``filescan()`` for externally mounted file systems.
|
||||
Nextcloud plug-in applications register actions with ``cron.php`` automatically to take care of typical housekeeping operations, such as garbage collecting of temporary files or checking for newly updated files using ``filescan()`` for externally mounted file systems.
|
||||
|
||||
Parameters
|
||||
----------
|
||||
@@ -23,7 +23,7 @@ You can schedule cron jobs in three ways -- using AJAX, Webcron, or cron. The de
|
||||
AJAX
|
||||
~~~~
|
||||
|
||||
The AJAX scheduling method is the default option. Unfortunately, however, it is also the least reliable. Each time a user visits the ownCloud page, a single background job is executed. The advantage of this mechanism is that it does not require access to the system nor registration with a third party service. The disadvantage of this mechanism, when compared to the Webcron service, is that it requires regular visits to the page for it to be triggered.
|
||||
The AJAX scheduling method is the default option. Unfortunately, however, it is also the least reliable. Each time a user visits the Nextcloud page, a single background job is executed. The advantage of this mechanism is that it does not require access to the system nor registration with a third party service. The disadvantage of this mechanism, when compared to the Webcron service, is that it requires regular visits to the page for it to be triggered.
|
||||
|
||||
.. note:: Especially when using the Activity App or external storages, where new
|
||||
files are added, updated or deleted one of the two methods below should be
|
||||
@@ -32,12 +32,12 @@ The AJAX scheduling method is the default option. Unfortunately, however, it is
|
||||
Webcron
|
||||
~~~~~~~
|
||||
|
||||
By registering your ownCloud ``cron.php`` script address at an external webcron
|
||||
By registering your Nextcloud ``cron.php`` script address at an external webcron
|
||||
service (for example, easyCron_), you ensure that background jobs are executed
|
||||
regularly. To use this type of service, your server you must be able to access
|
||||
your server using the Internet. For example::
|
||||
|
||||
URL to call: http[s]://<domain-of-your-server>/owncloud/cron.php
|
||||
URL to call: http[s]://<domain-of-your-server>/nextcloud/cron.php
|
||||
|
||||
Cron
|
||||
~~~~
|
||||
@@ -47,16 +47,14 @@ Using the operating system cron feature is the preferred method for executing re
|
||||
To run a cron job on a \*nix system, every 15 minutes, under the default Web server user (often, ``www-data`` or ``wwwrun``), you must set up the following cron job to call the **cron.php** script::
|
||||
|
||||
# crontab -u www-data -e
|
||||
*/15 * * * * php -f /var/www/owncloud/cron.php
|
||||
*/15 * * * * php -f /var/www/nextcloud/cron.php
|
||||
|
||||
You can verify if the cron job has been added and scheduled by executing::
|
||||
|
||||
# crontab -u www-data -l
|
||||
*/15 * * * * php -f /var/www/owncloud/cron.php
|
||||
*/15 * * * * php -f /var/www/nextcloud/cron.php
|
||||
|
||||
.. note:: You have to replace the path ``/var/www/owncloud/cron.php`` with the path to your current ownCloud installation.
|
||||
|
||||
.. note:: You have to make sure that ``php`` is found by ``cron``. Best practice is to expressly add the full path like ``/usr/bin/php``.
|
||||
.. note:: You have to replace the path ``/var/www/nextcloud/cron.php`` with the path to your current Nextcloud installation.
|
||||
|
||||
.. note:: On some systems it might be required to call **php-cli** instead of **php**.
|
||||
|
||||
|
||||
@@ -10,8 +10,8 @@ the default download locations:
|
||||
|
||||
<?php
|
||||
|
||||
"customclient_desktop" => "https://owncloud.org/sync-clients/",
|
||||
"customclient_android" => "https://play.google.com/store/apps/details?id=com.owncloud.android",
|
||||
"customclient_desktop" => "https://nextcloud.com/install/",
|
||||
"customclient_android" => "https://play.google.com/store/apps/details?id=com.nextcloud.client",
|
||||
"customclient_ios" => "https://itunes.apple.com/us/app/owncloud/id543672169?mt=8",
|
||||
|
||||
Simply replace the URLs with the links to your own preferred download repos.
|
||||
|
||||
@@ -98,8 +98,8 @@ achieved by a setting such as the following in the Apache VirtualHosts
|
||||
configuration::
|
||||
|
||||
<VirtualHost *:80>
|
||||
ServerName cloud.owncloud.com
|
||||
Redirect permanent / https://cloud.owncloud.com/
|
||||
ServerName cloud.nextcloud.com
|
||||
Redirect permanent / https://cloud.nextcloud.com/
|
||||
</VirtualHost>
|
||||
|
||||
.. _enable-hsts-label:
|
||||
@@ -117,7 +117,7 @@ This can be achieved by setting the following settings within the Apache
|
||||
VirtualHost file::
|
||||
|
||||
<VirtualHost *:443>
|
||||
ServerName cloud.owncloud.com
|
||||
ServerName cloud.nextcloud.com
|
||||
<IfModule mod_headers.c>
|
||||
Header always set Strict-Transport-Security "max-age=15552000; includeSubDomains; preload"
|
||||
</IfModule>
|
||||
|
||||
@@ -1,47 +1,47 @@
|
||||
Reverse Proxy Configuration
|
||||
===========================
|
||||
|
||||
ownCloud can be run through a reverse proxy, which can cache static assets such
|
||||
Nextcloud can be run through a reverse proxy, which can cache static assets such
|
||||
as images, CSS or JS files, move the load of handling HTTPS to a different
|
||||
server or load balance between multiple servers.
|
||||
|
||||
Defining Trusted Proxies
|
||||
------------------------
|
||||
|
||||
For security, you must explicitly define the proxy servers that ownCloud is to
|
||||
For security, you must explicitly define the proxy servers that Nextcloud is to
|
||||
trust. Connections from trusted proxies will be specially treated to get the
|
||||
real client information, for use in access control and logging. Parameters are
|
||||
configured in :file:`config/config.php`
|
||||
|
||||
Set the **trusted_proxies** parameter as an array of IP address to define the
|
||||
servers ownCloud should trust as proxies. This parameter provides protection
|
||||
servers Nextcloud should trust as proxies. This parameter provides protection
|
||||
against client spoofing, and you should secure those servers as you would your
|
||||
ownCloud server.
|
||||
Nextcloud server.
|
||||
|
||||
A reverse proxy can define HTTP headers with the original client IP address,
|
||||
and ownCloud can use those headers to retrieve that IP address. ownCloud uses
|
||||
and Nextcloud can use those headers to retrieve that IP address. Nextcloud uses
|
||||
the de-facto standard header 'X-Forwarded-For' by default, but this can be
|
||||
configured with the **forwarded_for_headers** parameter. This parameter is an
|
||||
array of PHP lookup strings, for example 'X-Forwarded-For' becomes
|
||||
'HTTP_X_FORWARDED_FOR'. Incorrectly setting this parameter may allow clients
|
||||
to spoof their IP address as visible to ownCloud, even when going through the
|
||||
to spoof their IP address as visible to Nextcloud, even when going through the
|
||||
trusted proxy! The correct value for this parameter is dependent on your
|
||||
proxy software.
|
||||
|
||||
Overwrite Parameters
|
||||
--------------------
|
||||
|
||||
The automatic hostname, protocol or webroot detection of ownCloud can fail in
|
||||
The automatic hostname, protocol or webroot detection of Nextcloud can fail in
|
||||
certain reverse proxy situations. This configuration allows the automatic detection
|
||||
to be manually overridden.
|
||||
|
||||
If ownCloud fails to automatically detect the hostname, protocol or webroot
|
||||
If Nextcloud fails to automatically detect the hostname, protocol or webroot
|
||||
you can use the **overwrite** parameters inside the :file:`config/config.php`.
|
||||
The **overwritehost** parameter is used to set the hostname of the proxy. You
|
||||
can also specify a port. The **overwriteprotocol** parameter is used to set the
|
||||
protocol of the proxy. You can choose between the two options **http** and
|
||||
**https**. The **overwritewebroot** parameter is used to set the absolute web
|
||||
path of the proxy to the ownCloud folder. When you want to keep the automatic
|
||||
path of the proxy to the Nextcloud folder. When you want to keep the automatic
|
||||
detection of one of the three parameters you can leave the value empty or don't
|
||||
set it. The **overwritecondaddr** parameter is used to overwrite the values
|
||||
dependent on the remote address. The value must be a **regular expression** of
|
||||
@@ -55,9 +55,9 @@ Example
|
||||
Multiple Domains Reverse SSL Proxy
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
If you want to access your ownCloud installation **http://domain.tld/owncloud**
|
||||
If you want to access your Nextcloud installation **http://domain.tld/nextcloud**
|
||||
via a multiple domains reverse SSL proxy
|
||||
**https://ssl-proxy.tld/domain.tld/owncloud** with the IP address **10.0.0.1**
|
||||
**https://ssl-proxy.tld/domain.tld/nextcloud** with the IP address **10.0.0.1**
|
||||
you can set the following parameters inside the :file:`config/config.php`.
|
||||
|
||||
::
|
||||
@@ -67,7 +67,7 @@ you can set the following parameters inside the :file:`config/config.php`.
|
||||
"trusted_proxies" => ['10.0.0.1'],
|
||||
"overwritehost" => "ssl-proxy.tld",
|
||||
"overwriteprotocol" => "https",
|
||||
"overwritewebroot" => "/domain.tld/owncloud",
|
||||
"overwritewebroot" => "/domain.tld/nextcloud",
|
||||
"overwritecondaddr" => "^10\.0\.0\.1$",
|
||||
);
|
||||
|
||||
|
||||
@@ -11,18 +11,18 @@ line:
|
||||
and unpack the tarball in the appropriate directories. (See
|
||||
:doc:`linux_installation` and :doc:`source_installation`.)
|
||||
|
||||
2. Change the ownership of your ``owncloud`` directory to your HTTP user, like
|
||||
2. Change the ownership of your ``nextcloud`` directory to your HTTP user, like
|
||||
this example for Debian/Ubuntu. You must run ``occ`` as your HTTP user; see
|
||||
:ref:`http_user_label`::
|
||||
|
||||
$ sudo chown -R www-data:www-data /var/www/owncloud/
|
||||
$ sudo chown -R www-data:www-data /var/www/nextcloud/
|
||||
|
||||
3. Use the ``occ`` command to complete your installation. This takes the place
|
||||
of running the graphical Installation Wizard::
|
||||
|
||||
$ cd /var/www/owncloud/
|
||||
$ cd /var/www/nextcloud/
|
||||
$ sudo -u www-data php occ maintenance:install --database
|
||||
"mysql" --database-name "owncloud" --database-user "root" --database-pass
|
||||
"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
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
===================================
|
||||
ownCloud Deployment Recommendations
|
||||
===================================
|
||||
====================================
|
||||
Nextcloud Deployment Recommendations
|
||||
====================================
|
||||
|
||||
What is the best way to install and maintain ownCloud? The answer to that is
|
||||
*"it depends"* because every ownCloud customer has their own
|
||||
particular needs and IT infrastructure. ownCloud and the LAMP stack are
|
||||
What is the best way to install and maintain Nextcloud? The answer to that is
|
||||
*"it depends"* because every Nextcloud customer has their own
|
||||
particular needs and IT infrastructure. Nextcloud and the LAMP stack are
|
||||
highly-configurable, so we will present three typical scenarios and make
|
||||
best-practice recommendations for both software and hardware.
|
||||
|
||||
@@ -12,10 +12,10 @@ General Recommendations
|
||||
-----------------------
|
||||
|
||||
.. note:: Whatever the size of your organization, always keep one thing in mind:
|
||||
the amount of data stored in ownCloud will only grow. Plan ahead.
|
||||
the amount of data stored in Nextcloud will only grow. Plan ahead.
|
||||
|
||||
Consider setting up a scale-out deployment, or using Federated Cloud Sharing to
|
||||
keep individual ownCloud instances to a manageable size.
|
||||
keep individual Nextcloud instances to a manageable size.
|
||||
|
||||
.. comment: Federating instances seems the best way to grow organically in
|
||||
an enterprise. A lookup server to tie all the instances together under a
|
||||
@@ -79,7 +79,7 @@ Authentication via an existing LDAP or Active Directory server.
|
||||
scale the DB.
|
||||
|
||||
* Backup
|
||||
Install owncloud, ownCloud data directory and database on Btrfs filesystem.
|
||||
Install owncloud, 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.
|
||||
|
||||
@@ -97,7 +97,7 @@ Authentication via an existing LDAP or Active Directory server.
|
||||
|
||||
* Authentication
|
||||
User authentication via one or several LDAP or Active Directory servers. (See
|
||||
`User Authentication with LDAP`_ for information on configuring ownCloud to
|
||||
`User Authentication with LDAP`_ for information on configuring Nextcloud to
|
||||
use LDAP and AD.)
|
||||
|
||||
* Session Management
|
||||
@@ -110,16 +110,16 @@ Authentication via an existing LDAP or Active Directory server.
|
||||
>> /etc/fstab``.
|
||||
|
||||
* Memory Caching
|
||||
A memcache speeds up server performance, and ownCloud supports four
|
||||
A memcache speeds up server performance, and Nextcloud supports four
|
||||
memcaches; refer to `Configuring Memory Caching`_ for information on
|
||||
selecting and configuring a memcache.
|
||||
|
||||
* Storage
|
||||
Local storage.
|
||||
|
||||
* ownCloud Edition
|
||||
Standard Edition. (See `ownCloud Server or Enterprise Edition`_ for
|
||||
comparisons of the ownCloud editions.)
|
||||
* Nextcloud Edition
|
||||
Standard Edition. (See `Nextcloud Server or Enterprise Edition`_ for
|
||||
comparisons of the Nextcloud editions.)
|
||||
|
||||
Mid-sized Enterprises
|
||||
---------------------
|
||||
@@ -201,7 +201,7 @@ Authentication via an existing LDAP or Active Directory server.
|
||||
* Authentication
|
||||
User authentication via one or several LDAP or Active Directory servers.
|
||||
(See `User Authentication with LDAP`_ for information on configuring
|
||||
ownCloud to use LDAP and AD.)
|
||||
Nextcloud to use LDAP and AD.)
|
||||
|
||||
* LDAP
|
||||
Read-only slaves should be deployed on every application server for
|
||||
@@ -217,7 +217,7 @@ Authentication via an existing LDAP or Active Directory server.
|
||||
>> /etc/fstab``.
|
||||
|
||||
* Memory Caching
|
||||
A memcache speeds up server performance, and ownCloud supports four
|
||||
A memcache speeds up server performance, and Nextcloud supports four
|
||||
memcaches; refer to `Configuring Memory Caching`_ for information on
|
||||
selecting and configuring a memcache.
|
||||
|
||||
@@ -225,9 +225,9 @@ Authentication via an existing LDAP or Active Directory server.
|
||||
Use an off-the-shelf NFS solution, such as IBM Elastic Storage or RedHat
|
||||
Ceph.
|
||||
|
||||
* ownCloud Edition
|
||||
Enterprise Edition. (See `ownCloud Server or Enterprise Edition`_ for
|
||||
comparisons of the ownCloud editions.)
|
||||
* Nextcloud Edition
|
||||
Enterprise Edition. (See `Nextcloud Server or Enterprise Edition`_ for
|
||||
comparisons of the Nextcloud editions.)
|
||||
|
||||
Large Enterprises and Service Providers
|
||||
---------------------------------------
|
||||
@@ -312,9 +312,9 @@ Authentication via an existing LDAP or Active Directory server, or SAML.
|
||||
Storage or RedHAT Ceph. Optionally, an S3 compatible object store can also
|
||||
be used.
|
||||
|
||||
* ownCloud Edition
|
||||
Enterprise Edition. (See `ownCloud Server or Enterprise Edition`_ for
|
||||
comparisons of the ownCloud editions.)
|
||||
* Nextcloud Edition
|
||||
Enterprise Edition. (See `Nextcloud Server or Enterprise Edition`_ for
|
||||
comparisons of the Nextcloud editions.)
|
||||
|
||||
Hardware Considerations
|
||||
-----------------------
|
||||
@@ -340,7 +340,7 @@ Pros:
|
||||
Cons:
|
||||
|
||||
* Fewer high availability options.
|
||||
* The amount of data in ownCloud tends to continually grow. Eventually a
|
||||
* The amount of data in Nextcloud tends to continually grow. Eventually a
|
||||
single machine will not scale; I/O performance decreases and becomes a
|
||||
bottleneck with multiple up- and downloads, even with solid-state drives.
|
||||
|
||||
@@ -382,7 +382,7 @@ A Single Master DB is Single Point of Failure, Does Not Scale
|
||||
|
||||
When master fails another slave can become master. However, the increased
|
||||
complexity carries some risks: Multi-master has the risk of split brain, and
|
||||
deadlocks. ownCloud tries to solve the problem of deadlocks with high-level
|
||||
deadlocks. Nextcloud tries to solve the problem of deadlocks with high-level
|
||||
file locking.
|
||||
|
||||
Software Considerations
|
||||
@@ -392,7 +392,7 @@ Operating System
|
||||
^^^^^^^^^^^^^^^^
|
||||
|
||||
We are dependent on distributions that offer an easy way to install the various
|
||||
components in up-to-date versions. ownCloud has a partnership with RedHat
|
||||
components in up-to-date versions. Nextcloud has a partnership with RedHat
|
||||
and SUSE for customers who need commercial support. Canonical, the parent
|
||||
company of Ubuntu Linux, also offers enterprise service and support. Debian
|
||||
and Ubuntu are free of cost, and include newer software packages. CentOS is the
|
||||
@@ -424,7 +424,7 @@ slave(s).
|
||||
each slave individually. Even then each migration might take several hours.
|
||||
Make sure you have enough disk space. You have been warned.
|
||||
|
||||
.. comment: Currently, ownCloud uses the utf8 character set with utf8_bin
|
||||
.. comment: Currently, Nextcloud uses the utf8 character set with utf8_bin
|
||||
collation on MySQL installations. As a result 4 byte UTF characters like
|
||||
emojis cannot be used. This can be fixed by [moving to
|
||||
utf8mb4/utf8mb4_bin](https://github.com/owncloud/core/issues/7030).
|
||||
@@ -442,7 +442,7 @@ What about the other DBMS?
|
||||
deployments. It is not adequate for production systems.
|
||||
* Microsoft SQL Server is not a supported option.
|
||||
* Oracle DB is the de facto standard at large enterprises and is fully
|
||||
supported with ownCloud Enterprise Edition only.
|
||||
supported with Nextcloud Enterprise Edition only.
|
||||
|
||||
File Storage
|
||||
------------
|
||||
@@ -463,7 +463,7 @@ Session Storage
|
||||
---------------
|
||||
|
||||
* Redis: provides persistence, nice graphical inspection tools available,
|
||||
supports ownCloud high-level file locking.
|
||||
supports Nextcloud high-level file locking.
|
||||
|
||||
* If Shibboleth is a requirement you must use Memcached, and it can also be
|
||||
used to scale-out shibd session storage (see `Memcache StorageService`_).
|
||||
@@ -489,7 +489,7 @@ References
|
||||
.. _Configuring Memory Caching:
|
||||
https://doc.owncloud.org/server/9.0/admin_manual/configuration_server/
|
||||
caching_configuration.html
|
||||
.. _ownCloud Server or Enterprise Edition:
|
||||
.. _Nextcloud Server or Enterprise Edition:
|
||||
https://owncloud.com/owncloud-server-or-enterprise-edition/
|
||||
.. _F5 Big-IP: https://f5.com/products/big-ip/
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ the last step to completing the installation is running the Installation
|
||||
Wizard.
|
||||
This is just three steps:
|
||||
|
||||
#. Point your Web browser to ``http://localhost/owncloud``
|
||||
#. Point your Web browser to ``http://localhost/nextcloud``
|
||||
#. Enter your desired administrator's username and password.
|
||||
#. Click **Finish Setup**.
|
||||
|
||||
@@ -146,7 +146,7 @@ Replace the ``ocpath`` variable with the path to your ownCloud directory, and
|
||||
replace the ``htuser`` and ``htgroup`` variables with your HTTP user and group::
|
||||
|
||||
#!/bin/bash
|
||||
ocpath='/var/www/owncloud'
|
||||
ocpath='/var/www/nextcloud'
|
||||
htuser='www-data'
|
||||
htgroup='www-data'
|
||||
rootuser='root'
|
||||
|
||||
@@ -12,29 +12,29 @@ 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
|
||||
in these examples for your installation::
|
||||
|
||||
semanage fcontext -a -t httpd_sys_rw_content_t '/var/www/html/owncloud/data'
|
||||
restorecon '/var/www/html/owncloud/data'
|
||||
semanage fcontext -a -t httpd_sys_rw_content_t '/var/www/html/owncloud/config'
|
||||
restorecon '/var/www/html/owncloud/config'
|
||||
semanage fcontext -a -t httpd_sys_rw_content_t '/var/www/html/owncloud/apps'
|
||||
restorecon '/var/www/html/owncloud/apps'
|
||||
semanage fcontext -a -t httpd_sys_rw_content_t '/var/www/html/nextcloud/data'
|
||||
restorecon '/var/www/html/nextcloud/data'
|
||||
semanage fcontext -a -t httpd_sys_rw_content_t '/var/www/html/nextcloud/config'
|
||||
restorecon '/var/www/html/nextcloud/config'
|
||||
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::
|
||||
|
||||
semanage fcontext -d -t httpd_sys_rw_content_t '/var/www/html/owncloud/data'
|
||||
restorecon '/var/www/html/owncloud/data'
|
||||
semanage fcontext -d -t httpd_sys_rw_content_t '/var/www/html/owncloud/config'
|
||||
restorecon '/var/www/html/owncloud/config'
|
||||
semanage fcontext -d -t httpd_sys_rw_content_t '/var/www/html/owncloud/apps'
|
||||
restorecon '/var/www/html/owncloud/apps'
|
||||
semanage fcontext -d -t httpd_sys_rw_content_t '/var/www/html/nextcloud/data'
|
||||
restorecon '/var/www/html/nextcloud/data'
|
||||
semanage fcontext -d -t httpd_sys_rw_content_t '/var/www/html/nextcloud/config'
|
||||
restorecon '/var/www/html/nextcloud/config'
|
||||
semanage fcontext -d -t httpd_sys_rw_content_t '/var/www/html/nextcloud/apps'
|
||||
restorecon '/var/www/html/nextcloud/apps'
|
||||
|
||||
If you have customized SELinux policies and these examples do not work, you must give the
|
||||
HTTP server write access to these directories::
|
||||
|
||||
/var/www/html/owncloud/data
|
||||
/var/www/html/owncloud/config
|
||||
/var/www/html/owncloud/apps
|
||||
/var/www/html/nextcloud/data
|
||||
/var/www/html/nextcloud/config
|
||||
/var/www/html/nextcloud/apps
|
||||
|
||||
Allow access to a remote database
|
||||
---------------------------------
|
||||
|
||||
Reference in New Issue
Block a user