Branding

Author: LukasReschke

admin_manual/configuration_database/linux_database_configuration.rst

@@ -2,11 +2,11 @@
 Database Configuration
 ======================
 
-ownCloud requires a database in which administrative data is stored. The following databases are currently supported:
+Nextcloud requires a database in which administrative data is stored. The following databases are currently supported:
 
 * `MySQL <http://www.mysql.com/>`_ / `MariaDB <https://mariadb.org/>`_
 * `PostgreSQL <http://www.postgresql.org/>`_
-* `Oracle <http://www.oracle.com/>`_ (ownCloud Enterprise edition only)
+* `Oracle <http://www.oracle.com/>`_
 
 The MySQL or MariaDB databases are the recommended database engines.
 
@@ -25,12 +25,12 @@ requires that you install and set up the server software first.
 MySQL / MariaDB with Binary Logging Enabled
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-ownCloud is currently using a ``TRANSACTION_READ_COMMITTED`` transaction isolation
+Nextcloud is currently using a ``TRANSACTION_READ_COMMITTED`` transaction isolation
 to avoid data loss under high load scenarios (e.g. by using the sync client with
 many clients/users and many parallel operations). This requires a disabled or
 correctly configured binary logging when using MySQL or MariaDB. Your system is
 affected if you see the following in your log file during the installation or
-update of ownCloud:
+update of Nextcloud:
 
  An unhandled exception has been thrown:
  exception 'PDOException' with message 'SQLSTATE[HY000]: General error: 1665 
@@ -65,7 +65,7 @@ for detailed information.
 
 Parameters
 ----------
-For setting up ownCloud to use any database, use the instructions in :doc:`../installation/installation_wizard`. You should not have to edit the respective values in the :file:`config/config.php`.  However, in special cases (for example, if you want to connect your ownCloud instance to a database created by a previous installation of ownCloud), some modification might be required.
+For setting up Nextcloud to use any database, use the instructions in :doc:`../installation/installation_wizard`. You should not have to edit the respective values in the :file:`config/config.php`.  However, in special cases (for example, if you want to connect your Nextcloud instance to a database created by a previous installation of Nextcloud), some modification might be required.
 
 Configuring a MySQL or MariaDB Database
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -74,7 +74,7 @@ If you decide to use a MySQL or MariaDB database, ensure the following:
 
 * That you have installed and enabled the pdo_mysql extension in PHP
 
-* That the **mysql.default_socket** points to the correct socket (if the database runs on the same server as ownCloud).
+* That the **mysql.default_socket** points to the correct socket (if the database runs on the same server as Nextcloud).
 
 .. note:: MariaDB is backwards compatible with MySQL.  All instructions work for both. You will not need to replace mysql with anything.
 
@@ -100,7 +100,7 @@ The PHP configuration in :file:`/etc/php5/conf.d/mysql.ini` could look like this
   mysql.trace_mode=Off
 
 Now you need to create a database user and the database itself by using the
-MySQL command line interface. The database tables will be created by ownCloud
+MySQL command line interface. The database tables will be created by Nextcloud
 when you login for the first time.
 
 To start the MySQL command line mode use::
@@ -112,14 +112,14 @@ Then a **mysql>** or **MariaDB [root]>** prompt will appear. Now enter the follo
 ::
 
   CREATE USER 'username'@'localhost' IDENTIFIED BY 'password';
-  CREATE DATABASE IF NOT EXISTS owncloud;
-  GRANT ALL PRIVILEGES ON owncloud.* TO 'username'@'localhost' IDENTIFIED BY 'password';
+  CREATE DATABASE IF NOT EXISTS nextcloud;
+  GRANT ALL PRIVILEGES ON nextcloud.* TO 'username'@'localhost' IDENTIFIED BY 'password';
 
 You can quit the prompt by entering::
 
   quit
 
-An ownCloud instance configured with MySQL would contain the hostname on which
+An Nextcloud instance configured with MySQL would contain the hostname on which
 the database is running, a valid username and password to access it, and the
 name of the database. The :file:`config/config.php` as created by the
 :doc:`../installation/installation_wizard` would therefore contain entries like
@@ -130,7 +130,7 @@ this:
   <?php
 
     "dbtype"        => "mysql",
-    "dbname"        => "owncloud",
+    "dbname"        => "nextcloud",
     "dbuser"        => "username",
     "dbpassword"    => "password",
     "dbhost"        => "localhost",
@@ -168,13 +168,13 @@ Then a **template1=#** prompt will appear. Now enter the following lines and con
 ::
 
   CREATE USER username CREATEDB;
-  CREATE DATABASE owncloud OWNER username;
+  CREATE DATABASE nextcloud OWNER username;
 
 You can quit the prompt by entering::
 
   \q
 
-An ownCloud instance configured with PostgreSQL would contain the path to the socket on
+An Nextcloud instance configured with PostgreSQL would contain the path to the socket on
 which the database is running as the hostname, the system username the php process is using,
 and an empty password to access it, and the name of the database. The :file:`config/config.php` as 
 created by the :doc:`../installation/installation_wizard` would therefore contain entries like
@@ -185,7 +185,7 @@ this:
   <?php
 
     "dbtype"        => "pgsql",
-    "dbname"        => "owncloud",
+    "dbname"        => "nextcloud",
     "dbuser"        => "username",
     "dbpassword"    => "",
     "dbhost"        => "/var/run/postgresql",
@@ -196,7 +196,7 @@ this:
 If you use another authentication method (not peer), you'll need to use the following steps to get the database setup:
 Now you need to create a database user and the database itself by using the
 PostgreSQL command line interface. The database tables will be created by
-ownCloud when you login for the first time.
+Nextcloud when you login for the first time.
 
 To start the postgres command line mode use::
 
@@ -215,7 +215,7 @@ You can quit the prompt by entering::
 
   \q
 
-An ownCloud instance configured with PostgreSQL would contain the hostname on
+An Nextcloud instance configured with PostgreSQL would contain the hostname on
 which the database is running, a valid username and password to access it, and
 the name of the database. The :file:`config/config.php` as created by the
 :doc:`../installation/installation_wizard` would therefore contain entries like
@@ -226,7 +226,7 @@ this:
   <?php
 
     "dbtype"        => "pgsql",
-    "dbname"        => "owncloud",
+    "dbname"        => "nextcloud",
     "dbuser"        => "username",
     "dbpassword"    => "password",
     "dbhost"        => "localhost",
@@ -246,7 +246,7 @@ refer to the manual of your database for how to raise the configuration options
 ``wait_timeout`` and/or ``max_allowed_packet``.
 
 Some shared hosters are not allowing the access to these config options. For such
-systems ownCloud is providing a ``dbdriveroptions`` configuration option within your
+systems Nextcloud is providing a ``dbdriveroptions`` configuration option within your
 :file:`config/config.php` where you can pass such options to the database driver.
 Please refer to :doc:`../configuration_server/config_sample_php_parameters` for an example.
 
@@ -302,12 +302,12 @@ the respective host name::
 Assuming the database server is installed on the same system you're running
 the command from, use::
 
-  psql -Uusername -downcloud
+  psql -Uusername -dnextcloud
 
 To access a MySQL installation on a different machine, add the -h option with
 the respective host name::
 
-  psql -Uusername -downcloud -h HOSTNAME
+  psql -Uusername -dnextcloud -h HOSTNAME
 
 ::
 
@@ -330,10 +330,10 @@ Useful SQL commands
   MySQL     : SHOW DATABASES;
   PostgreSQL: \l
 
-**Show ownCloud Tables in Database**::
+**Show Nextcloud Tables in Database**::
 
-  MySQL     : USE owncloud; SHOW TABLES;
-  PostgreSQL: \c owncloud; \d
+  MySQL     : USE nextcloud; SHOW TABLES;
+  PostgreSQL: \c nextcloud; \d
 
 **Quit Database**::
 

admin_manual/configuration_files/collaborative_documents_configuration.rst

@@ -48,4 +48,4 @@ If the mentioned test fails please make sure that:
 * your SELinux configuration is not blocking the execution of the binary
 * the PHP ``open_basedir`` is correctly configured to allow the access to the binary
 
-More hints why the test is failing can be found in your ``data/owncloud.log``.
+More hints why the test is failing can be found in your ``data/nextcloud.log``.

admin_manual/configuration_files/federated_cloud_sharing_configuration.rst

@@ -6,13 +6,7 @@ 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 Nextcloud servers, in effect 
 creating a cloud of Nextclouds.
-
-Sharing With ownCloud 8 and Older
----------------------------------
-
-Direct Federation shares (:ref:`label-direct-share-link`) are not supported in 
-ownCloud 8 and older, so you must create Federation shares with public links 
-(:ref:`label-public-link-share`). 
+ 
 
 .. _label-direct-share-link:   
 
@@ -75,9 +69,6 @@ exchanged. A red light means the connection failed.
 Creating Federation Shares via Public Link Share
 ------------------------------------------------
 
-You'll need to use a Public Link Share to create Federation shares with 
-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 Nextcloud to create a public link for you, and then 

admin_manual/configuration_files/previews_configuration.rst

@@ -16,7 +16,7 @@ By default, Nextcloud can generate previews for the following filetypes:
 * Cover of MP3 files
 * Text documents
 
-.. note:: Older versions of ownCloud also supported the preview generation
+.. note:: Older versions of Nextcloud also supported the preview generation
           of other file types such as PDF, SVG or various office documents.
           Due to security concerns those providers have been disabled by
           default and are considered unsupported.

admin_manual/configuration_mimetypes/mimetype_aliases.rst

@@ -2,16 +2,16 @@
 Mimetype Aliases
 ================
 
-ownCloud allows you to create aliases for mimetypes, so that you can display 
+Nextcloud allows you to create aliases for mimetypes, so that you can display 
 custom icons for files. For example, you might want a nice audio icon for audio 
 files instead of the default file icon.
 
-By default ownCloud is distributed with 
-``owncloud/resources/config/mimetypealiases.dist.json``.
-Do not modify this file, as it will be replaced when ownCloud is updated. 
-Instead, create your own ``owncloud/config/mimetypealiases.json`` 
+By default Nextcloud is distributed with 
+``nextcloud/resources/config/mimetypealiases.dist.json``.
+Do not modify this file, as it will be replaced when Nextcloud is updated. 
+Instead, create your own ``nextcloud/config/mimetypealiases.json`` 
 file with your custom aliases. Use the same syntax as in 
-``owncloud/resources/config/mimetypealiases.dist.json``.
+``nextcloud/resources/config/mimetypealiases.dist.json``.
 
 Once you have made changes to your ``mimetypealiases.json``, use the ``occ`` 
 command to propagate the changes through the system. This example is for 

admin_manual/configuration_mimetypes/mimetype_mapping.rst

@@ -1,13 +1,13 @@
 Mimetype mapping
 ================
 
-ownCloud allows administrators to specify the mapping of a file extension to a
+Nextcloud allows administrators to specify the mapping of a file extension to a
 mimetype. For example files ending in ``mp3`` map to ``audio/mpeg``. Which 
-then in turn allows ownCloud to show the audio icon.
+then in turn allows Nextcloud to show the audio icon.
 
-By default ownCloud comes with ``mimetypemapping.dist.json``. This is a
+By default Nextcloud comes with ``mimetypemapping.dist.json``. This is a
 simple json array.
 Administrators should not update this file as it will get replaced on upgrades
-of ownCloud. Instead the file ``mimetypemapping.json`` should be created and
+of Nextcloud. Instead the file ``mimetypemapping.json`` should be created and
 modified, this file has precedence over the shipped file. 
 

admin_manual/configuration_server/activity_configuration.rst

@@ -1,7 +1,7 @@
 Configuring the Activity App
 ============================
 
-You can configure your ownCloud server to automatically send out e-mail notifications
+You can configure your Nextcloud server to automatically send out e-mail notifications
 to your users for various events like:
 
 * A file or folder has been shared
@@ -16,12 +16,12 @@ Enabling the Activity App
 -------------------------
 
 The Activity App is shipped and enabled by default. If it is not enabled
-simply go to your ownCloud Apps page to enable it.
+simply go to your Nextcloud Apps page to enable it.
 
-Configuring your ownCloud for the Activity App
+Configuring your Nextcloud for the Activity App
 ----------------------------------------------
 
-To configure your ownCloud to send out e-mail notifications a working
+To configure your Nextcloud to send out e-mail notifications a working
 :doc:`email_configuration` is mandatory.
 
 Furthermore it is recommended to configure the background job ``Webcron`` or

admin_manual/configuration_server/antivirus_configuration.rst

@@ -1,20 +1,20 @@
 Configuring the ClamAV Antivirus Scanner
 ========================================
 
-You can configure your ownCloud server to automatically run a virus scan on
+You can configure your Nextcloud server to automatically run a virus scan on
 newly-uploaded files with the Antivirus App for Files. The Antivirus App for
 Files integrates the open source anti-virus engine `ClamAV
-<http://www.clamav.net/index.html>`_  with ownCloud. ClamAV detects all forms
+<http://www.clamav.net/index.html>`_  with Nextcloud. ClamAV detects all forms
 of malware including Trojan horses, viruses, and worms, and it operates on all
 major file types including Windows, Linux, and Mac files, compressed files,
 executables, image files, Flash, PDF, and many others. ClamAV's Freshclam
 daemon automatically updates its malware signature database at scheduled
 intervals.
 
 ClamAV runs on Linux and any Unix-type operating system, and Microsoft Windows.
-However, it has only been tested with ownCloud on Linux, so these instructions
+However, it has only been tested with Nextcloud on Linux, so these instructions
 are for Linux systems. You must first install ClamAV, and then install and
-configure the Antivirus App for Files on ownCloud.
+configure the Antivirus App for Files on Nextcloud.
 
 Installing ClamAV
 -----------------
@@ -77,14 +77,14 @@ and ``freshclam.conf`` until it is running the way you want.
 Enabling the Antivirus App for Files
 ------------------------------------
 
-Simply go to your ownCloud Apps page to enable it.
+Simply go to your Nextcloud Apps page to enable it.
 
 .. figure:: ../images/antivirus-app.png
 
-Configuring ClamAV on ownCloud
+Configuring ClamAV on Nextcloud
 ------------------------------
 
-Next, go to your ownCloud Admin page and set your ownCloud logging level to
+Next, go to your Nextcloud Admin page and set your Nextcloud logging level to
 Everything.
 
 .. figure:: ../images/antivirus-logging.png
@@ -95,21 +95,21 @@ Now find your Antivirus Configuration panel on your Admin page.
 
 ClamAV runs in one of three modes:
 
-* Daemon (Socket): ClamAV is running on the same server as ownCloud. The ClamAV
+* Daemon (Socket): ClamAV is running on the same server as Nextcloud. The ClamAV
   daemon, ``clamd``, runs in the background. When there is no activity ``clamd``
   places a minimal load on your system. If your users upload large volumes of
   files you will see high CPU usage.
 
 * Daemon: ClamAV is running on a different server. This is a good option
-  for ownCloud servers with high volumes of file uploads.
+  for Nextcloud servers with high volumes of file uploads.
 
-* Executable: ClamAV is running on the same server as ownCloud, and the
+* Executable: ClamAV is running on the same server as Nextcloud, and the
   ``clamscan`` command is started and then stopped with each file upload.
   ``clamscan`` is slow and not always reliable for on-demand usage; it is
   better to use one of the daemon modes.
 
 Daemon (Socket)
-  ownCloud should detect your ``clamd`` socket and fill in the ``Socket``
+  Nextcloud should detect your ``clamd`` socket and fill in the ``Socket``
   field. This is the ``LocalSocket`` option in ``clamd.conf``. You can
   run ``netstat`` to verify::
 
@@ -135,7 +135,7 @@ Daemon
 
 Executable
   The Executable option requires the path to ``clamscan``, which is the
-  interactive ClamAV scanning command. ownCloud should find it automatically.
+  interactive ClamAV scanning command. Nextcloud should find it automatically.
 
   .. figure:: ../images/antivirus-executable.png