From 30ba29b94fae5065231fbf2c1c9b42539c1deec9 Mon Sep 17 00:00:00 2001 From: Patric Lenhart Date: Sat, 18 Jun 2016 01:14:35 +0200 Subject: [PATCH] changed more ownCloud references to Nextcloud --- .../automatic_configuration.rst | 16 +++++----- .../background_jobs_configuration.rst | 8 ++--- .../custom_client_repos.rst | 4 +-- .../configuration_server/harden_server.rst | 6 ++-- .../reverse_proxy_configuration.rst | 6 ++-- .../command_line_installation.rst | 8 ++--- .../deployment_recommendations.rst | 2 +- .../installation/installation_wizard.rst | 4 +-- .../installation/selinux_configuration.rst | 30 +++++++++---------- 9 files changed, 42 insertions(+), 42 deletions(-) diff --git a/admin_manual/configuration_server/automatic_configuration.rst b/admin_manual/configuration_server/automatic_configuration.rst index 8bee4e8f3..d07d31213 100644 --- a/admin_manual/configuration_server/automatic_configuration.rst +++ b/admin_manual/configuration_server/automatic_configuration.rst @@ -7,10 +7,10 @@ to set up each instance separately as described in 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. +: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 "/www/htdocs/owncloud/data", + "directory" => "/www/htdocs/nextcloud/data", ); @@ -50,7 +50,7 @@ Using the following parameter settings, the "Finish setup" screen requests data "sqlite", - "dbname" => "owncloud", + "dbname" => "nextcloud", "dbtableprefix" => "", ); @@ -63,7 +63,7 @@ Using the following parameter settings, the "Finish setup" screen requests data "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 "pgsql", - "dbname" => "owncloud", + "dbname" => "nextcloud", "dbuser" => "username", "dbpass" => "password", "dbhost" => "localhost", @@ -104,14 +104,14 @@ Using the following parameter settings, because all parameters are already confi "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 diff --git a/admin_manual/configuration_server/background_jobs_configuration.rst b/admin_manual/configuration_server/background_jobs_configuration.rst index 3fa77ddfc..abeb407c0 100644 --- a/admin_manual/configuration_server/background_jobs_configuration.rst +++ b/admin_manual/configuration_server/background_jobs_configuration.rst @@ -37,7 +37,7 @@ 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]:///owncloud/cron.php + URL to call: http[s]:///nextcloud/cron.php Cron ~~~~ @@ -47,14 +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 Nextcloud installation. +.. 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**. diff --git a/admin_manual/configuration_server/custom_client_repos.rst b/admin_manual/configuration_server/custom_client_repos.rst index 41e687d3c..1a402c233 100644 --- a/admin_manual/configuration_server/custom_client_repos.rst +++ b/admin_manual/configuration_server/custom_client_repos.rst @@ -10,8 +10,8 @@ the default download locations: "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. diff --git a/admin_manual/configuration_server/harden_server.rst b/admin_manual/configuration_server/harden_server.rst index 6c536c838..17e9b8630 100644 --- a/admin_manual/configuration_server/harden_server.rst +++ b/admin_manual/configuration_server/harden_server.rst @@ -99,8 +99,8 @@ achieved by a setting such as the following in the Apache VirtualHosts config: :: - ServerName cloud.owncloud.com - Redirect permanent / https://cloud.owncloud.com/ + ServerName cloud.nextcloud.com + Redirect permanent / https://cloud.nextcloud.com/ .. _enable-hsts-label: @@ -118,7 +118,7 @@ This can be achieved by setting the following settings within the Apache VirtualHost file:: - ServerName cloud.owncloud.com + ServerName cloud.nextcloud.com Header always set Strict-Transport-Security "max-age=15768000; includeSubDomains; preload" diff --git a/admin_manual/configuration_server/reverse_proxy_configuration.rst b/admin_manual/configuration_server/reverse_proxy_configuration.rst index fa83ceaf3..952b5a3e4 100644 --- a/admin_manual/configuration_server/reverse_proxy_configuration.rst +++ b/admin_manual/configuration_server/reverse_proxy_configuration.rst @@ -55,9 +55,9 @@ Example Multiple Domains Reverse SSL Proxy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -If you want to access your Nextcloud 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$", ); diff --git a/admin_manual/installation/command_line_installation.rst b/admin_manual/installation/command_line_installation.rst index c04e7ebfc..05e7dc760 100644 --- a/admin_manual/installation/command_line_installation.rst +++ b/admin_manual/installation/command_line_installation.rst @@ -10,18 +10,18 @@ line: 1. Download and install the Nextcloud code via your package manager, or download and unpack the tarball in the appropriate directories. (See :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" Nextcloud is not installed - only a limited number of commands are available Nextcloud was successfully installed diff --git a/admin_manual/installation/deployment_recommendations.rst b/admin_manual/installation/deployment_recommendations.rst index 82d561583..4313220f3 100644 --- a/admin_manual/installation/deployment_recommendations.rst +++ b/admin_manual/installation/deployment_recommendations.rst @@ -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 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. diff --git a/admin_manual/installation/installation_wizard.rst b/admin_manual/installation/installation_wizard.rst index e742feee9..251f6d3c4 100644 --- a/admin_manual/installation/installation_wizard.rst +++ b/admin_manual/installation/installation_wizard.rst @@ -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 Nextcloud 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' diff --git a/admin_manual/installation/selinux_configuration.rst b/admin_manual/installation/selinux_configuration.rst index abeb1d115..1a797bed8 100644 --- a/admin_manual/installation/selinux_configuration.rst +++ b/admin_manual/installation/selinux_configuration.rst @@ -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 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/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 ---------------------------------