mirrors/nextcloud-documentation
3
0
Fork 0
mirror of https://github.com/nextcloud/documentation.git synced 2025-10-26 11:18:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #22 from Zollak/oc-references

Browse Source 
changed more ownCloud references to Nextcloud
This commit is contained in:
Marius Blüm 2016-06-18 08:41:23 +02:00 committed by GitHub
commit b9dff267a7
9 changed files with 42 additions and 42 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
admin_manual/configuration_server/automatic_configuration.rst
View File

@ -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
<?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",
@ -104,14 +104,14 @@ Using the following parameter settings, because all parameters are already confi
<?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

8
admin_manual/configuration_server/background_jobs_configuration.rst
View File

@ -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]://<domain-of-your-server>/owncloud/cron.php
URL to call: http[s]://<domain-of-your-server>/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**.

4
admin_manual/configuration_server/custom_client_repos.rst
View File

@ -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.

6
admin_manual/configuration_server/harden_server.rst
View File

@ -99,8 +99,8 @@ achieved by a setting such as the following in the Apache VirtualHosts config:
::
<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:
@ -118,7 +118,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=15768000; includeSubDomains; preload"
</IfModule>

6
admin_manual/configuration_server/reverse_proxy_configuration.rst
View File

@ -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$",
);

8
admin_manual/installation/command_line_installation.rst
View File

@ -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

2
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 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.

4
admin_manual/installation/installation_wizard.rst
View File

@ -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'

30
admin_manual/installation/selinux_configuration.rst
View File

@ -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
---------------------------------