diff --git a/README.md b/README.md index 0e38f6d7a..275f4e899 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -# ownCloud Server Documentation +# ownCloud Classic Documentation **IMPORTANT** @@ -11,11 +11,11 @@ Since April 2026, this repository requires [Commit Signing](https://docs.github. * [Generating the Documentation](#generating-the-documentation) * [Target Branch and Backporting](#target-branch-and-backporting) * [Branching Workflow](#branching-workflow) -* [Create a New Version Branch for ownCloud Server](#create-a-new-version-branch-for-owncloud-server) +* [Create a New Version Branch for ownCloud Classic](#create-a-new-version-branch-for-owncloud-server) ## Building the Server Docs -The ownCloud Server documentation is not built independently. Instead, it is built together with the [main documentation](https://github.com/owncloud/docs/). However, you can build a local copy of the ownCloud Server documentation to preview changes you are making. +The ownCloud Classic documentation is not built independently. Instead, it is built together with the [main documentation](https://github.com/owncloud/docs/). However, you can build a local copy of the ownCloud Classic documentation to preview changes you are making. Whenever a Pull Request of this repo gets merged, it automatically triggers a full docs build. @@ -33,8 +33,8 @@ See the [following section](https://github.com/owncloud/docs#target-branch-and-b ## Branching Workflow -Please refer to the [Branching Workflow for ownCloud Server](./docs/the-branching-workflow.md) for more information. +Please refer to the [Branching Workflow for ownCloud Classic](./docs/the-branching-workflow.md) for more information. -## Create a New Version Branch for ownCloud Server +## Create a New Version Branch for ownCloud Classic -Please refer to [Create a New Version Branch for ownCloud Server](./docs/new-version-branch.md) for more information. +Please refer to [Create a New Version Branch for ownCloud Classic](./docs/new-version-branch.md) for more information. diff --git a/antora.yml b/antora.yml index e0f960f99..0d0e0b51b 100644 --- a/antora.yml +++ b/antora.yml @@ -1,5 +1,5 @@ name: server -title: ownCloud Server +title: ownCloud Classic version: '10.15' start_page: ROOT:index.adoc nav: diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index 6fb681377..520de7ebe 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -1,3 +1,3 @@ -= Introduction to ownCloud Server += Introduction to ownCloud Classic -Welcome to the ownCloud Server documentation. These documents provide an xref:admin_manual:index.adoc[admin guide] with information for installation, configuration and administrative tasks as well as documentation for xref:developer_manual:index.adoc[developers]. An xref:classic_ui:index.adoc[ownCloud User Manual] for the server is provided in the web documentation. +Welcome to the ownCloud Classic documentation. These documents provide an xref:admin_manual:index.adoc[admin guide] with information for installation, configuration and administrative tasks as well as documentation for xref:developer_manual:index.adoc[developers]. An xref:classic_ui:index.adoc[ownCloud User Manual] for the server is provided in the web documentation. diff --git a/modules/admin_manual/pages/configuration/integration/splunk.adoc b/modules/admin_manual/pages/configuration/integration/splunk.adoc index 9a55a79cb..863d0dfca 100644 --- a/modules/admin_manual/pages/configuration/integration/splunk.adoc +++ b/modules/admin_manual/pages/configuration/integration/splunk.adoc @@ -17,10 +17,10 @@ The app makes all relevant ownCloud data available in Splunk. The dashboards and == Prerequisites To set up the _ownCloud App for Splunk_, a number of prerequisites have to be fulfilled. -* ownCloud Server has a minimum version of 10.5. +* ownCloud Classic has a minimum version of 10.5. * Splunk has a minimum version of 7.2. -* The {oc-marketplace-url}/apps/metrics[_Metrics App_] is installed, configured and enabled on ownCloud Server. -* The {oc-marketplace-url}/apps/admin_audit[_Auditing App_] is installed, configured and enabled on ownCloud Server. +* The {oc-marketplace-url}/apps/metrics[_Metrics App_] is installed, configured and enabled on ownCloud Classic. +* The {oc-marketplace-url}/apps/admin_audit[_Auditing App_] is installed, configured and enabled on ownCloud Classic. * Both components of the _ownCloud App for Splunk_ , the app and the add-on, are installed and configured. See below for further information on these components. == Setup & Configuration @@ -66,11 +66,11 @@ On your Universal Forwarder or Heavy Forwarder instance, you must enable input u . Copy `$SPLUNK_HOME/etc/apps/TA_owncloud/default/inputs.conf.example` to `$SPLUNK_HOME/etc/apps/TA_owncloud/local` directory and rename the file to `inputs.conf`. . Open `$SPLUNK_HOME/etc/apps/TA_owncloud/local/inputs.conf` for editing. . Check all `index = owncloud` settings and change the index name if needed. -. Check the ownCloud logs locations (default: `/var/www/owncloud/data/`) and change them to the values you configured on the ownCloud Server. +. Check the ownCloud logs locations (default: `/var/www/owncloud/data/`) and change them to the values you configured on the ownCloud Classic server. . Save the `$SPLUNK_HOME/etc/apps/TA_owncloud/local/inputs.conf` file. . Copy `$SPLUNK_HOME/etc/apps/TA_owncloud/default/owncloud.conf.example` to `$SPLUNK_HOME/etc/apps/TA_owncloud/local` directory and rename the file to `owncloud.conf`. . Open `$SPLUNK_HOME/etc/apps/TA_owncloud/local/owncloud.conf` for editing. -. Change the `METRICSAPIKEY` setting to the Metrics API key value you configured on the ownCloud Server. +. Change the `METRICSAPIKEY` setting to the Metrics API key value you configured on the ownCloud Classic server. . Change the `API_HOST` setting to your ownCloud instance domain name or IP address. This value is used to query the Metrics API for data. . Save the `$SPLUNK_HOME/etc/apps/TA_owncloud/local/owncloud.conf` file. . Restart the Splunk instance. diff --git a/modules/admin_manual/pages/configuration/server/harden_server.adoc b/modules/admin_manual/pages/configuration/server/harden_server.adoc index 8d7aa2530..e9c77d1a7 100644 --- a/modules/admin_manual/pages/configuration/server/harden_server.adoc +++ b/modules/admin_manual/pages/configuration/server/harden_server.adoc @@ -10,7 +10,7 @@ ownCloud aims to ship with secure defaults that do not need to get modified by administrators. However, in some cases some additional security hardening can be applied in scenarios were the administrator has complete control over the ownCloud instance. This page assumes that -you run ownCloud Server on Apache2 in a Linux environment. +you run ownCloud Classic on Apache2 in a Linux environment. NOTE: ownCloud will warn you in the administration interface if some critical security-relevant options are missing. However, it is still up to the server administrator to review and maintain system security. diff --git a/modules/admin_manual/pages/configuration/server/oc_server_tuning.adoc b/modules/admin_manual/pages/configuration/server/oc_server_tuning.adoc index b349773b3..a0578dab6 100644 --- a/modules/admin_manual/pages/configuration/server/oc_server_tuning.adoc +++ b/modules/admin_manual/pages/configuration/server/oc_server_tuning.adoc @@ -1,4 +1,4 @@ -= ownCloud Server Tuning += ownCloud Classic Tuning :toc: right :memcached-url: https://memcached.org :thp-url: https://www.kernel.org/doc/Documentation/vm/transhuge.txt diff --git a/modules/admin_manual/pages/configuration/server/occ_commands/app_commands/_metrics_commands.adoc b/modules/admin_manual/pages/configuration/server/occ_commands/app_commands/_metrics_commands.adoc index 7559e1e74..e3813fd12 100644 --- a/modules/admin_manual/pages/configuration/server/occ_commands/app_commands/_metrics_commands.adoc +++ b/modules/admin_manual/pages/configuration/server/occ_commands/app_commands/_metrics_commands.adoc @@ -2,7 +2,7 @@ Marketplace URL: {oc-marketplace-url}/apps/metrics[Metrics] -Monitoring and reporting of ownCloud Server. For details please see the +Monitoring and reporting of ownCloud Classic. For details please see the xref:enterprise/reporting/metrics.adoc[Metrics] documentation. Set a secret for authenticating requests at the endpoint. diff --git a/modules/admin_manual/pages/configuration/server/occ_commands/app_commands/_wnd_commands.adoc b/modules/admin_manual/pages/configuration/server/occ_commands/app_commands/_wnd_commands.adoc index a08c6415f..0a7501d90 100644 --- a/modules/admin_manual/pages/configuration/server/occ_commands/app_commands/_wnd_commands.adoc +++ b/modules/admin_manual/pages/configuration/server/occ_commands/app_commands/_wnd_commands.adoc @@ -103,7 +103,7 @@ Process the notifications stored by the `wnd:listen` command == Set the Service Account -NOTE: This command is deprecated starting with ownCloud 10.8. All mount options marked as _password_ are now encrypted by default. Existing old settings are migrated automatically. +NOTE: This command is deprecated starting with ownCloud Classic 10.8. All mount options marked as _password_ are now encrypted by default. Existing old settings are migrated automatically. Sets the service account for the target mount point. You'll be asked for the password of the service account. diff --git a/modules/admin_manual/pages/configuration/server/occ_commands/core_commands/_command_line_upgrade_commands.adoc b/modules/admin_manual/pages/configuration/server/occ_commands/core_commands/_command_line_upgrade_commands.adoc index 49706a2c9..16e9a159c 100644 --- a/modules/admin_manual/pages/configuration/server/occ_commands/core_commands/_command_line_upgrade_commands.adoc +++ b/modules/admin_manual/pages/configuration/server/occ_commands/core_commands/_command_line_upgrade_commands.adoc @@ -16,7 +16,7 @@ upgrade [options] [width="100%",cols="20%,70%",] |=== -| `--major` | Automatically update apps to new major versions during minor updates of ownCloud Server. +| `--major` | Automatically update apps to new major versions during minor updates of ownCloud Classic. | `--no-app-disable` | Skip disabling of third party apps. |=== diff --git a/modules/admin_manual/pages/configuration/server/occ_commands/core_commands/_database_commands.adoc b/modules/admin_manual/pages/configuration/server/occ_commands/core_commands/_database_commands.adoc index e156ecb26..e024967f5 100644 --- a/modules/admin_manual/pages/configuration/server/occ_commands/core_commands/_database_commands.adoc +++ b/modules/admin_manual/pages/configuration/server/occ_commands/core_commands/_database_commands.adoc @@ -38,7 +38,7 @@ Convert charset of MySQL/MariaDB to use utf8mb4. If you are using an older ownCl == Restore the Table Format -This command sets the default row format of MySQL/MariaDB tables. This is only necessary once before you are going to e.g. install MariaDB 10.6 or higher because the COMPRESSED row format is now read-only by default. As a prerequisite, ownCloud 10.9 needs to be installed first. See the xref:maintenance/upgrading/database_upgrade.adoc[Database Upgrade] guide for details. +This command sets the default row format of MySQL/MariaDB tables. This is only necessary once before you are going to e.g. install MariaDB 10.6 or higher because the COMPRESSED row format is now read-only by default. As a prerequisite, ownCloud Classic 10.9 needs to be installed first. See the xref:maintenance/upgrading/database_upgrade.adoc[Database Upgrade] guide for details. [source,bash,subs="attributes+"] ---- diff --git a/modules/admin_manual/pages/configuration/server/occ_commands/core_commands/_encryption_commands.adoc b/modules/admin_manual/pages/configuration/server/occ_commands/core_commands/_encryption_commands.adoc index 9fd848c3d..0f5b89699 100644 --- a/modules/admin_manual/pages/configuration/server/occ_commands/core_commands/_encryption_commands.adoc +++ b/modules/admin_manual/pages/configuration/server/occ_commands/core_commands/_encryption_commands.adoc @@ -170,7 +170,7 @@ The `-y` switch can be supplied to automate acceptance of user input. `encryption:fix-encrypted-version` fixes the encrypted version of files if the encrypted file(s) are not downloadable for a given user. You only need this command if you get an "Invalid Signature" message in the browser or the clients. -Background: the `oc_filecache` database table contains the integer columns "version" and "encryptedVersion" which start with 1 and are incremented on every file modification. When using encryption, those values are used together with the ciphertext to generate a cryptographic signature for the file. The version value is required to verify the signature. In some very rare cases like timeouts or bugs etc., the value might not get updated accordingly or get lost. The brute-force approach is to use the `fix:encrypted:version` command until the file can be decrypted. Starting with ownCloud 10.8, the behavior of the command got improved so that the encryptedVersion value is reset to its original value if no correct version was found. Before that fix, the last tried value was stored in the database thus modifying the state of the system and making further rescue attempts non-deterministic. +Background: the `oc_filecache` database table contains the integer columns "version" and "encryptedVersion" which start with 1 and are incremented on every file modification. When using encryption, those values are used together with the ciphertext to generate a cryptographic signature for the file. The version value is required to verify the signature. In some very rare cases like timeouts or bugs etc., the value might not get updated accordingly or get lost. The brute-force approach is to use the `fix:encrypted:version` command until the file can be decrypted. Starting with ownCloud Classic 10.8, the behavior of the command got improved so that the encryptedVersion value is reset to its original value if no correct version was found. Before that fix, the last tried value was stored in the database thus modifying the state of the system and making further rescue attempts non-deterministic. === Arguments diff --git a/modules/admin_manual/pages/configuration/server/ui-configuration.adoc b/modules/admin_manual/pages/configuration/server/ui-configuration.adoc index 35747c805..ad2b6550f 100644 --- a/modules/admin_manual/pages/configuration/server/ui-configuration.adoc +++ b/modules/admin_manual/pages/configuration/server/ui-configuration.adoc @@ -9,7 +9,7 @@ The web UI can be configured for optimal user experience. === Hide the Upload Estimation -Note that this setting is available for ownCloud Server only. +Note that this setting is available for ownCloud Classic only. When uploading a document, an upload estimation (progress bar) is shown like in the example below: diff --git a/modules/admin_manual/pages/configuration/user/oidc/kopano-setup.adoc b/modules/admin_manual/pages/configuration/user/oidc/kopano-setup.adoc index 2cd1a242f..a2aeae970 100644 --- a/modules/admin_manual/pages/configuration/user/oidc/kopano-setup.adoc +++ b/modules/admin_manual/pages/configuration/user/oidc/kopano-setup.adoc @@ -16,7 +16,7 @@ The sections below will explain these areas and provide configuration examples u For the configuration examples, let's assume we have: -- ownCloud Server available as `+https://cloud.example.com+` +- ownCloud Classic available as `+https://cloud.example.com+` - Kopano Konnect available as `+https://idp.example.com+` === Set Up and Configure Kopano @@ -31,9 +31,9 @@ Specifically, you have to: TIP: Kopano Konnect can be set up via Docker. Images are available on Docker Hub (`kopano/konnectd`). -=== Configure ownCloud Server +=== Configure ownCloud Classic -To set up ownCloud Server to work with OpenID Connect, you have to: +To set up ownCloud Classic to work with OpenID Connect, you have to: 1. Install the {oc-marketplace-url}/apps/openidconnect[OpenID Connect App] 2. Configure `config.php` @@ -44,7 +44,7 @@ TIP: It is recommended to first figure out all configurations on a test system a ==== List of OpenID Connect config.php Parameters Follow this link to read more about the -xref:configuration/server/config_apps_sample_php_parameters.adoc#app-openid-connect-oidc[OIDC config.php parameters] available to configure OpenID Connect on ownCloud Server. +xref:configuration/server/config_apps_sample_php_parameters.adoc#app-openid-connect-oidc[OIDC config.php parameters] available to configure OpenID Connect on ownCloud Classic. ==== Example config.php diff --git a/modules/admin_manual/pages/configuration/user/oidc/ms-azure-setup.adoc b/modules/admin_manual/pages/configuration/user/oidc/ms-azure-setup.adoc index c95ca8545..58aaf3ad6 100644 --- a/modules/admin_manual/pages/configuration/user/oidc/ms-azure-setup.adoc +++ b/modules/admin_manual/pages/configuration/user/oidc/ms-azure-setup.adoc @@ -83,9 +83,9 @@ When it comes to use `127.0.0.1` instead of `localhost` as Redirect URI, the tas image:configuration/user/oidc/ms-azure-ad/ms-azure-manifest.png[width=500] -=== Configure ownCloud Server +=== Configure ownCloud Classic -To set up ownCloud Server to work with OpenID Connect, you have to: +To set up ownCloud Classic to work with OpenID Connect, you have to: 1. Install the {oc-marketplace-url}/apps/openidconnect[OpenID Connect App]. 2. Configure `config.php`. @@ -96,7 +96,7 @@ TIP: It is recommended to first figure out all configurations on a test system a ==== List of OpenID Connect config.php Parameters Follow this link to read more about the -xref:configuration/server/config_apps_sample_php_parameters.adoc#app-openid-connect-oidc[OIDC config.php parameters] available to configure OpenID Connect on ownCloud Server. +xref:configuration/server/config_apps_sample_php_parameters.adoc#app-openid-connect-oidc[OIDC config.php parameters] available to configure OpenID Connect on ownCloud Classic. ==== Example config.php Setup @@ -145,7 +145,7 @@ If you want to let ownCloud create users which are not present during a OIDC aut === Use oAuth2 authentication for ownCloud Desktop and Mobile Clients -To allow the ownCloud clients (ownCloud Web, Desktop, Android and iOS) to interact with the ownCloud Server, you have to install and enable the oAuth2 app. Please see the xref:configuration/server/security/oauth2.adoc[Open Authentication (OAuth2)] for more details. In this setup, your ownCloud Clients will work without extra hassles, but please be advised that the ownCloud Server is acting as identity provider for the clients and you will not be able to delete those clients directly from your identity management solution. +To allow the ownCloud clients (ownCloud Web, Desktop, Android and iOS) to interact with the ownCloud Classic server, you have to install and enable the oAuth2 app. Please see the xref:configuration/server/security/oauth2.adoc[Open Authentication (OAuth2)] for more details. In this setup, your ownCloud Clients will work without extra hassles, but please be advised that the ownCloud Classic server is acting as identity provider for the clients and you will not be able to delete those clients directly from your identity management solution. === Register ownCloud Desktop and Mobile Clients with Azure AD diff --git a/modules/admin_manual/pages/configuration/user/oidc/oidc.adoc b/modules/admin_manual/pages/configuration/user/oidc/oidc.adoc index e5f55cee9..d00365edc 100644 --- a/modules/admin_manual/pages/configuration/user/oidc/oidc.adoc +++ b/modules/admin_manual/pages/configuration/user/oidc/oidc.adoc @@ -30,7 +30,7 @@ link to get more details on the flow sequence. == Supported Identity Providers -ownCloud Server can work with identity providers (IdP) that support OpenID Connect. There are many identity providers available and the OpenID Connect implementations vary a lot in terms of supported features as well as configuration needs. +ownCloud Classic can work with identity providers (IdP) that support OpenID Connect. There are many identity providers available and the OpenID Connect implementations vary a lot in terms of supported features as well as configuration needs. The currently supported products are @@ -47,12 +47,12 @@ Please get in touch with ownCloud Consulting if you need help with a specific id == Prerequisites -Setting up ownCloud Server to work with OpenID Connect requires a couple of components to work together: +Setting up ownCloud Classic to work with OpenID Connect requires a couple of components to work together: - An external identity provider configured to work with the ownCloud components - A distributed memcache setup - such as Redis or Memcached - is required to operate this app. Follow the xref:configuration/server/caching_configuration.adoc[caching documentation] on how to set it up. -- The {oc-marketplace-url}/apps/openidconnect[OpenID Connect App] installed on ownCloud Server -- Configuration settings in `config.php` on ownCloud Server +- The {oc-marketplace-url}/apps/openidconnect[OpenID Connect App] installed on ownCloud Classic +- Configuration settings in `config.php` on ownCloud Classic + * `'http.cookie.samesite' \=> 'None',` + @@ -98,7 +98,7 @@ NOTE: Only set either the database or the config.php keys but not both for the O . Webserver Service Discovery Information + -In order to allow the ownCloud Clients (Desktop/Android/iOS) to make use of OpenID Connect, the webserver serving ownCloud Server needs to _provide service discovery information_ under the following static path: +In order to allow the ownCloud Clients (Desktop/Android/iOS) to make use of OpenID Connect, the webserver serving ownCloud Classic needs to _provide service discovery information_ under the following static path: + [source,url] ---- @@ -260,7 +260,7 @@ ownCloud desktop and mobile apps come with default `scope` and `prompt` paramete === Migrate Clients from Basic Authentication to OIDC -If your users are logged in to their desktop and mobile clients via basic authentication (username/password) against ownCloud Server and you are not using OAuth2 to authorize the ownCloud clients, a migration to OIDC can be conducted as follows: +If your users are logged in to their desktop and mobile clients via basic authentication (username/password) against ownCloud Classic and you are not using OAuth2 to authorize the ownCloud clients, a migration to OIDC can be conducted as follows: 1. Make sure you have a working OIDC configuration based on the above sections. 2. Enable the OpenID Connect App. diff --git a/modules/admin_manual/pages/configuration/user/oidc/onelogin-setup.adoc b/modules/admin_manual/pages/configuration/user/oidc/onelogin-setup.adoc index dd814f877..87c6ec9be 100644 --- a/modules/admin_manual/pages/configuration/user/oidc/onelogin-setup.adoc +++ b/modules/admin_manual/pages/configuration/user/oidc/onelogin-setup.adoc @@ -43,9 +43,9 @@ image:configuration/user/oidc/onelogin/onelogin-oidc-configuration.png[width=90% + image:configuration/user/oidc/onelogin/onelogin-oidc-sso.png[width=90%] -=== Configure ownCloud Server +=== Configure ownCloud Classic -These are the generic steps to set up ownCloud Server to work with OpenID Connect, for details see the sections below: +These are the generic steps to set up ownCloud Classic to work with OpenID Connect, for details see the sections below: 1. Install the {oc-marketplace-url}/apps/openidconnect[OpenID Connect App]. 2. Configure `config.php`. @@ -56,7 +56,7 @@ TIP: It is recommended to first figure out all configurations on a test system a ==== List of OpenID Connect config.php Parameters Follow this link to read more about the -xref:configuration/server/config_apps_sample_php_parameters.adoc#app-openid-connect-oidc[OIDC config.php parameters] available to configure OpenID Connect on ownCloud Server. +xref:configuration/server/config_apps_sample_php_parameters.adoc#app-openid-connect-oidc[OIDC config.php parameters] available to configure OpenID Connect on ownCloud Classic. ==== Example config.php Setup diff --git a/modules/admin_manual/pages/configuration/user/user_auth_ldap.adoc b/modules/admin_manual/pages/configuration/user/user_auth_ldap.adoc index a196d9b2e..8fd00ff9d 100644 --- a/modules/admin_manual/pages/configuration/user/user_auth_ldap.adoc +++ b/modules/admin_manual/pages/configuration/user/user_auth_ldap.adoc @@ -620,7 +620,7 @@ Since ownCloud 8.0.10 and up the home folder rule is enforced. This means that o {occ-command-example-prefix} config:app:set user_ldap enforce_home_folder_naming_rule --value=1 ---- -Starting with ownCloud 10.0, the home folder naming rule is only applied when first provisioning the user. This prevents data loss due to re-provisioning the users home folder in case of unintentional changes in LDAP. +Starting with ownCloud Classic 10.0, the home folder naming rule is only applied when first provisioning the user. This prevents data loss due to re-provisioning the users home folder in case of unintentional changes in LDAP. -- === Expert Settings diff --git a/modules/admin_manual/pages/enterprise/authentication/kerberos.adoc b/modules/admin_manual/pages/enterprise/authentication/kerberos.adoc index af192ba3c..196b8f49a 100644 --- a/modules/admin_manual/pages/enterprise/authentication/kerberos.adoc +++ b/modules/admin_manual/pages/enterprise/authentication/kerberos.adoc @@ -128,7 +128,7 @@ The administration server. This is typically the same as the LDAP/Active Directo // https://docs.typo3.org/p/causal/ig_ldap_sso_auth/2.1/en-us/AdministratorManual/ConfigureApacheKerberos.html -=== ownCloud Server Side +=== ownCloud Classic Side //// * The host the ownCloud instance is running on must be part of the domain. @@ -373,7 +373,7 @@ samba-tool domain exportkeytab --principal=HTTP/ /.keytab` to the Linux server hosting the ownCloud instance to location ``. Note that the file must be accessible by the web server. -== Configure ownCloud Server +== Configure ownCloud Classic Follow these steps on the server running ownCloud: diff --git a/modules/admin_manual/pages/enterprise/collaboration/collabora_secure_view.adoc b/modules/admin_manual/pages/enterprise/collaboration/collabora_secure_view.adoc index 78ed5c7d9..3c158493b 100644 --- a/modules/admin_manual/pages/enterprise/collaboration/collabora_secure_view.adoc +++ b/modules/admin_manual/pages/enterprise/collaboration/collabora_secure_view.adoc @@ -7,7 +7,7 @@ Collabora Online allows you to work with all kinds of Collabora office documents directly in your browser. This application can connect to a Collabora Online (or other) server (WOPI-like client) where ownCloud is the WOPI host. -When Collabora Online is properly set up and integrated into ownCloud Server, secure view functionality is available. Secure view is a mode where users can place limitations on files and folders that are shared. +When Collabora Online is properly set up and integrated into ownCloud Classic, secure view functionality is available. Secure view is a mode where users can place limitations on files and folders that are shared. These limitations can include: diff --git a/modules/admin_manual/pages/enterprise/collaboration/msoffice-wopi-integration.adoc b/modules/admin_manual/pages/enterprise/collaboration/msoffice-wopi-integration.adoc index e5ec793ca..a4de568e0 100644 --- a/modules/admin_manual/pages/enterprise/collaboration/msoffice-wopi-integration.adoc +++ b/modules/admin_manual/pages/enterprise/collaboration/msoffice-wopi-integration.adoc @@ -135,10 +135,10 @@ More information about this issue is available in the following links: Checklist if something is not working: -. **Client** can reach the **ownCloud Server** (browse to web page and log in) +. **Client** can reach the **ownCloud Classic** (browse to web page and log in) . **Client** can reach the **Office Online Server** (via hosting/discovery url with https) -. **ownCloud Server** can reach the **Office Online Server** (via hosting/discovery url with https) -. **Office Online Server** can reach **ownCloud Server** (browse to web page and log in) +. **ownCloud Classic** can reach the **Office Online Server** (via hosting/discovery url with https) +. **Office Online Server** can reach **ownCloud Classic** (browse to web page and log in) Make sure TLS 1.2 is being used: diff --git a/modules/admin_manual/pages/enterprise/external_storage/windows-network-drive_configuration.adoc b/modules/admin_manual/pages/enterprise/external_storage/windows-network-drive_configuration.adoc index 7a61be2d2..9673cd2c5 100644 --- a/modules/admin_manual/pages/enterprise/external_storage/windows-network-drive_configuration.adoc +++ b/modules/admin_manual/pages/enterprise/external_storage/windows-network-drive_configuration.adoc @@ -312,7 +312,7 @@ NOTE: The capability of the listener depends on the ability of the used SMB/CIFS ==== WND Listener Setup -The WND listener for ownCloud 10 includes two different commands that need to be executed: +The WND listener for ownCloud Classic 10 includes two different commands that need to be executed: * xref:wndlisten[wnd:listen] Listen to changes and save them in the database * xref:wndprocess-queue[wnd:process-queue] Process saved listener changes from the database @@ -694,7 +694,7 @@ export HOME=/var/lib/apache2 Restart Apache, open your ownCloud Admin page and start creating SMB/CIFS mounts. -=== Basic Setup for One ownCloud Server +=== Basic Setup for One ownCloud Classic . Go to the admin settings and set up the required WND mounts. Be aware though, that there are some limitations. These are: .. ownCloud needs access to the Windows account password for the mounts to update the file cache properly. This means that "__login credentials, saved in session__" won't work with the listener. ownCloud suggests to use "__login credentials, saved in DB__" as the best replacement instead. diff --git a/modules/admin_manual/pages/enterprise/file_management/files_lifecycle.adoc b/modules/admin_manual/pages/enterprise/file_management/files_lifecycle.adoc index aad06616c..0675e1266 100644 --- a/modules/admin_manual/pages/enterprise/file_management/files_lifecycle.adoc +++ b/modules/admin_manual/pages/enterprise/file_management/files_lifecycle.adoc @@ -41,7 +41,7 @@ By default, archived files are stored within the ownCloud data directory but out === Setting Upload Times for Existing Files -File Lifecycle Management uses the _upload time_ of files (server time at which they first appeared on the ownCloud server) to determine when to archive them. As ownCloud Server generally does not store this metadata, the File Lifecycle Management extension takes care of this when it is enabled. +File Lifecycle Management uses the _upload time_ of files (server time at which they first appeared on the ownCloud server) to determine when to archive them. As ownCloud Classic generally does not store this metadata, the File Lifecycle Management extension takes care of this when it is enabled. When File Lifecycle Management is set up on an existing ownCloud installation, you therefore have to set an _upload time_ for all files that existed before the extension has been enabled. The same applies if it was temporarily disabled. Only then can the archiving policies work. To set an upload time for all files that do not yet have one, you can use the _occ_ command `lifecycle:set-upload-time`. diff --git a/modules/admin_manual/pages/enterprise/installation/install.adoc b/modules/admin_manual/pages/enterprise/installation/install.adoc index 22015afa5..6e857858a 100644 --- a/modules/admin_manual/pages/enterprise/installation/install.adoc +++ b/modules/admin_manual/pages/enterprise/installation/install.adoc @@ -7,7 +7,7 @@ After you have completed your initial installation of ownCloud as detailed in the README, follow the instructions in xref:installation/installation_wizard.adoc[The Installation Wizard] to finish setting up ownCloud. To upgrade your Enterprise server, refer to -xref:maintenance/upgrade.adoc[How to Upgrade Your ownCloud Server]. +xref:maintenance/upgrade.adoc[How to Upgrade Your ownCloud Classic]. == Manual Installation diff --git a/modules/admin_manual/pages/enterprise/reporting/metrics.adoc b/modules/admin_manual/pages/enterprise/reporting/metrics.adoc index 1b4c07389..0db37108d 100644 --- a/modules/admin_manual/pages/enterprise/reporting/metrics.adoc +++ b/modules/admin_manual/pages/enterprise/reporting/metrics.adoc @@ -8,7 +8,7 @@ The {oc-marketplace-url}/apps/metrics[Metrics App] provides a building block for reporting of ownCloud Server. For simple use cases, it ships with an integrated dashboard that summarizes information about users, storage as well as shares and allows exporting it to a CSV file. Additionally, it adds a -Metrics HTTP API endpoint to ownCloud Server, which can be used to obtain the Metrics data in regular +Metrics HTTP API endpoint to ownCloud Classic, which can be used to obtain the Metrics data in regular intervals. Thus, more sophisticated analysis and visualizations can be conducted. The Metrics data are provided as snapshot values in the JSON format and are optimized to be consumed by diff --git a/modules/admin_manual/pages/enterprise/security/ransomware-protection.adoc b/modules/admin_manual/pages/enterprise/security/ransomware-protection.adoc index 60360cf29..90cc29c4f 100644 --- a/modules/admin_manual/pages/enterprise/security/ransomware-protection.adoc +++ b/modules/admin_manual/pages/enterprise/security/ransomware-protection.adoc @@ -21,7 +21,7 @@ there is no guarantee that the attackers will supply the key after payment is made. To help mitigate such threats and ensure ongoing access to user data, ownCloud provides the Ransomware Protection app. -NOTE: It is essential to be aware that user data needs to be synchronized with you ownCloud Server using the +NOTE: It is essential to be aware that user data needs to be synchronized with you ownCloud Classic using the ownCloud Desktop synchronization client. Data that is not synchronized and stored in ownCloud cannot be protected. == About Ransomware Protection @@ -106,7 +106,7 @@ future-proof protection from ransomware attacks: retaining data and providing the means to roll back to a particular point in time. ownCloud Ransomware Protection will, therefore, record all changes on an -ownCloud Server and allow administrators to rollback user data to a +ownCloud Classic and allow administrators to rollback user data to a particular point in time, making use of ownCloud’s integrated Versioning and Trash bin features. @@ -124,7 +124,7 @@ Ransomware prevention and protection reduces risks to a minimum acceptable level | Ransomware Prevention (Blocker) | -| First line of defense against ransomware attacks. Ransomware Protection uses a file name pattern blacklist to prevent uploading files that have file extensions associated with ransomware (e.g. `.crypt`) thereby preserving the original files on the ownCloud Server. +| First line of defense against ransomware attacks. Ransomware Protection uses a file name pattern blacklist to prevent uploading files that have file extensions associated with ransomware (e.g. `.crypt`) thereby preserving the original files on the ownCloud Classic server. | Ransomguard Scanner | `occ ransomguard:scan ` diff --git a/modules/admin_manual/pages/index.adoc b/modules/admin_manual/pages/index.adoc index c19a946d1..927221d8d 100644 --- a/modules/admin_manual/pages/index.adoc +++ b/modules/admin_manual/pages/index.adoc @@ -2,7 +2,7 @@ :owncloud-news-url: https://owncloud.com/news/ :ownCloud-channel-url: https://www.youtube.com/channel/UC_4gez4lsWqciH-otOlXo5w -Welcome to the ownCloud Classic Server Administration Guide. This guide describes administration tasks for ownCloud, the flexible open source file synchronization and sharing solution. ownCloud includes the ownCloud server, which runs on Linux, plus client applications for Microsoft Windows, Mac OS X, Linux, Android and Apple iOS operating systems. +Welcome to the ownCloud Classic Administration Guide. This guide describes administration tasks for ownCloud, the flexible open source file synchronization and sharing solution. ownCloud includes the ownCloud server, which runs on Linux, plus client applications for Microsoft Windows, Mac OS X, Linux, Android and Apple iOS operating systems. Current editions of ownCloud manuals are always available online at {docs-base-url}[doc.owncloud.com]. diff --git a/modules/admin_manual/pages/installation/deployment_recommendations.adoc b/modules/admin_manual/pages/installation/deployment_recommendations.adoc index 1eaf1e85e..db871592f 100644 --- a/modules/admin_manual/pages/installation/deployment_recommendations.adoc +++ b/modules/admin_manual/pages/installation/deployment_recommendations.adoc @@ -155,7 +155,7 @@ Local storage or Network File System (NFS) if already available. ==== Recommended Licensing Model * Standard or Enterprise Edition -* See {owncloud-edition-url}[ownCloud Server or Enterprise Edition] for comparisons of the ownCloud editions. +* See {owncloud-edition-url}[ownCloud Classic or Enterprise Edition] for comparisons of the ownCloud editions. == Scenario 2: Mid-Sized Enterprises @@ -245,7 +245,7 @@ You may take a look on the {netapp-nfs-bpg-url}[NetApp NFS Best Practice and Imp ==== Recommended Licensing Model * Enterprise Edition -* See {owncloud-edition-url}[ownCloud Server or Enterprise Edition] for comparisons of the ownCloud editions. +* See {owncloud-edition-url}[ownCloud Classic or Enterprise Edition] for comparisons of the ownCloud editions. == Scenario 3: Large Enterprises and Service Providers @@ -335,7 +335,7 @@ You may take a look on the {netapp-nfs-bpg-url}[NetApp NFS Best Practice and Imp ==== Recommended Licensing Model * Enterprise Edition -* See {owncloud-edition-url}[ownCloud Server or Enterprise Edition] for comparisons of the ownCloud editions. +* See {owncloud-edition-url}[ownCloud Classic or Enterprise Edition] for comparisons of the ownCloud editions. ==== Redis Configuration diff --git a/modules/admin_manual/pages/installation/docker/index.adoc b/modules/admin_manual/pages/installation/docker/index.adoc index ad5fe3642..eab1377c3 100644 --- a/modules/admin_manual/pages/installation/docker/index.adoc +++ b/modules/admin_manual/pages/installation/docker/index.adoc @@ -371,12 +371,12 @@ The file `docker-compose.yml` contains the configuration of your ownCloud contai [NOTE] ==== -Since ownCloud Server 10.5, the dedicated enterprise docker image `registry.owncloud.com/owncloud/enterprise` is deprecated. All supported enterprise features and apps are now included in the public image `owncloud/server` available on Docker Hub. A login to our registry `registry.owncloud.com` is no longer required. +Since ownCloud Classic 10.5, the dedicated enterprise docker image `registry.owncloud.com/owncloud/enterprise` is deprecated. All supported enterprise features and apps are now included in the public image `owncloud/server` available on Docker Hub. A login to our registry `registry.owncloud.com` is no longer required. ==== [source,yaml] ---- -include::example$installation/docker/docker-compose.yml[Example Docker Compose YAML configuration file for ownCloud Server.] +include::example$installation/docker/docker-compose.yml[Example Docker Compose YAML configuration file for ownCloud Classic.] ---- == Troubleshooting diff --git a/modules/admin_manual/pages/installation/index.adoc b/modules/admin_manual/pages/installation/index.adoc index 8a68cd5a0..3d45f85e2 100644 --- a/modules/admin_manual/pages/installation/index.adoc +++ b/modules/admin_manual/pages/installation/index.adoc @@ -3,13 +3,13 @@ == Introduction -This is an overview about the possible installation options for ownCloud Server. You can install ownCloud Server manually or use a Docker-based installation. +This is an overview about the possible installation options for ownCloud Classic. You can install ownCloud Classic manually or use a Docker-based installation. == Manual Installation * The xref:installation/manual_installation/manual_installation.adoc[Detailed Installation Guide] is a thorough guide for installing ownCloud, containing all the information needed for the prerequisites, the dependencies, the actual installation and the configuration afterwards. The example installation is based on Ubuntu Server. + -This guide covers Ubuntu server preparations like dependencies, required packages and other necessary components or configurations including Ubuntu upgrades if necessary, descriptions, explanations and easy copy and paste example commands where possible. You will also get directed to other necessary or recommended sections in the documentation to have a well working ownCloud Server base ready for production. +This guide covers Ubuntu server preparations like dependencies, required packages and other necessary components or configurations including Ubuntu upgrades if necessary, descriptions, explanations and easy copy and paste example commands where possible. You will also get directed to other necessary or recommended sections in the documentation to have a well working ownCloud Classic base ready for production. * The xref:installation/quick_guides/ubuntu_20_04.adoc[Quick Installation Guide] is a quick guide for installing ownCloud. This guide cannot go into details and has its limits by nature. If you experience issues like with dependencies of PHP or other relevant things like the operating system, web server or database, you have to use the xref:installation/manual_installation/manual_installation.adoc[Detailed Installation Guide]. diff --git a/modules/admin_manual/pages/installation/manual_installation/manual_installation_db.adoc b/modules/admin_manual/pages/installation/manual_installation/manual_installation_db.adoc index cb65c0346..eee39ceef 100644 --- a/modules/admin_manual/pages/installation/manual_installation/manual_installation_db.adoc +++ b/modules/admin_manual/pages/installation/manual_installation/manual_installation_db.adoc @@ -9,7 +9,7 @@ to other databases! == Possible Databases -When installing ownCloud Server & ownCloud Enterprise editions, the administrator may choose one of four supported database products. These are: +When installing ownCloud Classic & ownCloud Enterprise editions, the administrator may choose one of four supported database products. These are: * SQLite * MYSQL/MariaDB (recommended) @@ -29,7 +29,7 @@ SQLite has no client synchronization support, so other devices will not be able == MYSQL/MariaDB -MariaDB is the ownCloud recommended database. It may be used with either ownCloud Server or ownCloud Enterprise editions. Please look for additional configuration parameters in the xref:configuration/database/linux_database_configuration.adoc[Database Configuration on Linux] guides. +MariaDB is the ownCloud recommended database. It may be used with either ownCloud Classic or ownCloud Enterprise editions. Please look for additional configuration parameters in the xref:configuration/database/linux_database_configuration.adoc[Database Configuration on Linux] guides. Once the database installation is complete, refer to the Database section in the xref:configuration/server/harden_server.adoc#database[Hardening and Security Guidance] guide for additional important information. diff --git a/modules/admin_manual/pages/installation/manual_installation/manual_installation_prerequisites.adoc b/modules/admin_manual/pages/installation/manual_installation/manual_installation_prerequisites.adoc index 08acf35d3..1e7861d58 100644 --- a/modules/admin_manual/pages/installation/manual_installation/manual_installation_prerequisites.adoc +++ b/modules/admin_manual/pages/installation/manual_installation/manual_installation_prerequisites.adoc @@ -1,6 +1,6 @@ = Prerequisites for Manual Installation on Linux :toc: right -:description: This document guides you through the prerequisites for a manual ownCloud Server installation on Linux. +:description: This document guides you through the prerequisites for a manual ownCloud Classic installation on Linux. :avconv-url: https://libav.org/ :ffmpeg-url: https://ffmpeg.org/ diff --git a/modules/admin_manual/pages/installation/system_requirements.adoc b/modules/admin_manual/pages/installation/system_requirements.adoc index 4e42d051e..adf8cf3d1 100644 --- a/modules/admin_manual/pages/installation/system_requirements.adoc +++ b/modules/admin_manual/pages/installation/system_requirements.adoc @@ -6,7 +6,7 @@ :ios-system-requirements-url: https://doc.owncloud.com/ios-app/ios_faq.html :android-system-requirements-url: https://doc.owncloud.com/android/faq.html -:description: Read this documentation for a recommended or supported environment for your ownCloud Server. This documentation applies to both a new installation or upgrade of an existing installation. +:description: Read this documentation for a recommended or supported environment for your ownCloud Classic server. This documentation applies to both a new installation or upgrade of an existing installation. == Introduction diff --git a/modules/admin_manual/pages/maintenance/encryption/migrating-from-user-key-to-master-key.adoc b/modules/admin_manual/pages/maintenance/encryption/migrating-from-user-key-to-master-key.adoc index 521d7bbdc..5c2a9efe7 100644 --- a/modules/admin_manual/pages/maintenance/encryption/migrating-from-user-key-to-master-key.adoc +++ b/modules/admin_manual/pages/maintenance/encryption/migrating-from-user-key-to-master-key.adoc @@ -5,7 +5,7 @@ == Introduction -IMPORTANT: User Key Encryption has been deprecated with ownCloud Server 10.7, see the corresponding https://doc.owncloud.com/server_release_notes.html#deprecation-note-for-user-key-storage-encryption[release notes] for details. Though you can continue to use this solution, it is no longer selectable and existing User Key Encryption must be migrated to Master Key Encryption. +IMPORTANT: User Key Encryption has been deprecated with ownCloud Classic 10.7, see the corresponding https://doc.owncloud.com/server_release_notes.html#deprecation-note-for-user-key-storage-encryption[release notes] for details. Though you can continue to use this solution, it is no longer selectable and existing User Key Encryption must be migrated to Master Key Encryption. The reason disabling User key-based encryption is because of some disadvantages. It blocks some additional functions such as the integration of an online editor like LibreOffice or OnlyOffice into ownCloud and can cause problems when sharing files with groups. See xref:configuration/files/encryption/encryption_configuration.adoc#limitations-of-user-key-based-encryption[Limitations of User-Key Based Encryption] for more details. Master-key-based encryption is therefore now the recommended and only available setup for all new installations. diff --git a/modules/admin_manual/pages/maintenance/migrating_to_ocis.adoc b/modules/admin_manual/pages/maintenance/migrating_to_ocis.adoc index 803b0cf66..cc51f28bf 100644 --- a/modules/admin_manual/pages/maintenance/migrating_to_ocis.adoc +++ b/modules/admin_manual/pages/maintenance/migrating_to_ocis.adoc @@ -1,17 +1,17 @@ = Migrating to ownCloud Infinite Scale :toc: right :toclevels: 3 -:description: This guide describes how to migrate an ownCloud 10 instance to ownCloud Infinite Scale (oCIS) using the migrate-to-ocis app and its occ commands. +:description: This guide describes how to migrate an ownCloud Classic instance to ownCloud Infinite Scale (oCIS) using the migrate-to-ocis app and its occ commands. == Introduction {description} -The migration transfers users, groups, files, and shares from an ownCloud 10 (OC10) instance to a target oCIS instance in a series of sequential steps. The OC10 server is not modified by the migration — it remains operational throughout most of the process. +The migration transfers users, groups, files, and shares from an ownCloud Classic instance to a target oCIS instance in a series of sequential steps. The ownCloud Classic server is not modified by the migration — it remains operational throughout most of the process. == Overview -The migration works with an app to be installed on the ownCloud 10 side. The app is provided by ownCloud as part of the guided migration. Please contact {oc-support-url}[ownCloud support] to get it. +The migration works with an app to be installed on the ownCloud Classic side. The app is provided by ownCloud as part of the guided migration. Please contact {oc-support-url}[ownCloud support] to get it. Both instances need to be fully configured and running, and they must be reachable from each other. @@ -51,19 +51,19 @@ External mount data is excluded by the file migration step. These mounts must be * *User passwords*: Migrated users are created with an unknown password and cannot log in normally after migration. The admin must set up a temporary password or onboarding process for each user. -* *Share link passwords*: Passwords for migrated share links will be unknown and will not match the original OC10 passwords. Users should change the passwords of all their share links after the migration. +* *Share link passwords*: Passwords for migrated share links will be unknown and will not match the original ownCloud Classic passwords. Users should change the passwords of all their share links after the migration. -* *Passwordless share links*: By default, oCIS requires a password for share links. Passwordless links from OC10 will fail to migrate unless the oCIS policy is changed. Set the environment variable `OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD=false` on the oCIS instance before migration if you need to migrate passwordless links. +* *Passwordless share links*: By default, oCIS requires a password for share links. Passwordless links from ownCloud Classic will fail to migrate unless the oCIS policy is changed. Set the environment variable `OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD=false` on the oCIS instance before migration if you need to migrate passwordless links. == Prerequisites -=== ownCloud 10 +=== ownCloud Classic [IMPORTANT] ==== * *Shell/SSH access to the ownCloud server* is required. All migration steps use `occ` commands. -* The *ownCloud-provided _migrate-to-ocis_ app must be installed* on the OC10 instance: +* The *ownCloud-provided _migrate-to-ocis_ app must be installed* on the ownCloud Classic instance: ** This app comes bundled with its own copy of rclone. ** See the xref:installation/apps_management_installation.adoc[Installing and Managing Apps] documentation for details. @@ -113,7 +113,7 @@ AUTH_APP_ENABLE_IMPERSONATION: true No data migration can be initiated until users and groups are available on the oCis side. To avoid a failing data migration step, no user or group changes, such as adding, deleting or changing, must be applied after this migration step. -Different steps are required for the migration of users and groups, depending on their location in OC10, to make them accessible to oCIS. +Different steps are required for the migration of users and groups, depending on their location in ownCloud Classic, to make them accessible to oCIS. Consider that the https://doc.owncloud.com/ocis/next/deployment/services/s-list/idm.html[internal IDM] provided by oCIS, which is a mini LDAP, has a very limited scope and is mainly targeted at small Infinite Scale installations or testing. It should therefore not be used in production environments. For larger setups or production environments, it is highly recommended to use a “real” LDAP server or to switch to an external Identity Management Solution instead. @@ -121,17 +121,17 @@ To address these different requirements, migrating users and groups are divided === Migrate With Local Users -These steps describe the migration of local OC10 users and groups to an external LDAP or to the embedded oCIS IDM - where no external LDAP is used. +These steps describe the migration of local ownCloud Classic users and groups to an external LDAP or to the embedded oCIS IDM - where no external LDAP is used. ==== Migrate Local Users to LDAP -If you have local users and groups in OC10 and wish to use an external LDAP server that oCIS is connected to — which is highly recommended for production environments — you must migrate these users and groups manually before proceeding to the xref:#migrate-files-and-shares[Migrate Files and Shares] section. Please note that user and group names must match. Check the additional requirements in xref:#migration-with-ldap-users[Migration With LDAP Users]. +If you have local users and groups in ownCloud Classic and wish to use an external LDAP server that oCIS is connected to — which is highly recommended for production environments — you must migrate these users and groups manually before proceeding to the xref:#migrate-files-and-shares[Migrate Files and Shares] section. Please note that user and group names must match. Check the additional requirements in xref:#migration-with-ldap-users[Migration With LDAP Users]. As the next step, continue with xref:#preparing-data-migration[Preparing Data Migration]. ==== Migrate Local Users to IDM -Migrate OC10 users and groups to oCIS internal IDM, no extrernal LDAP server used. As a prerequisite, run the steps in xref:#preparing-data-migration[Preparing Data Migration] first. +Migrate ownCloud Classic users and groups to oCIS internal IDM, no extrernal LDAP server used. As a prerequisite, run the steps in xref:#preparing-data-migration[Preparing Data Migration] first. Migrate Users:: + @@ -145,7 +145,7 @@ sudo -u www-data \ migrate:to-ocis:migrate:users admin ---- -New users are created in oCIS to match the OC10 users. If a user already exists in oCIS (for example the `admin` account), the existing account will be reused. +New users are created in oCIS to match the ownCloud Classic users. If a user already exists in oCIS (for example the `admin` account), the existing account will be reused. -- Assign a Role:: @@ -160,10 +160,10 @@ sudo -u www-data \ migrate:to-ocis:assign-role admin ---- -The same role is assigned to all migrated OC10 users, except the oCIS admin. OC10 roles are not preserved during migration — all users receive a single role regardless of their original OC10 role. For most installations the `User` role is the appropriate choice. +The same role is assigned to all migrated ownCloud Classic users, except the oCIS admin. ownCloud Classic roles are not preserved during migration — all users receive a single role regardless of their original ownCloud Classic role. For most installations the `User` role is the appropriate choice. -NOTE: OC10 admin users who are members of the OC10 `admin` group will have that group membership migrated to oCIS, but they will not receive oCIS admin privileges unless the assigned role grants them. The oCIS admin must manually set the appropriate oCIS role for any user that should have elevated permissions after migration. + -OC10 subadmin privileges have no equivalent role in oCIS and are not migrated. +NOTE: ownCloud Classic admin users who are members of the ownCloud Classic `admin` group will have that group membership migrated to oCIS, but they will not receive oCIS admin privileges unless the assigned role grants them. The oCIS admin must manually set the appropriate oCIS role for any user that should have elevated permissions after migration. + +ownCloud Classic subadmin privileges have no equivalent role in oCIS and are not migrated. This step is mandatory and cannot be skipped. -- @@ -171,7 +171,7 @@ This step is mandatory and cannot be skipped. Migrate Groups:: + -- -Migrate the OC10 groups and their user memberships to oCIS. The admin password is asked interactively: +Migrate the ownCloud Classic groups and their user memberships to oCIS. The admin password is asked interactively: [source,bash] ---- @@ -187,11 +187,11 @@ As the final step, continue with xref:#migrate-files-and-shares[Migrate Files an === Migration With LDAP Users -In general, users and groups must be accessible to oCIS. This can be achieved either connecting oCIS to the same LDAP server, or by migrating users and groups from the LDAP server that OC10 is connected to to a different backend for oCIS. +In general, users and groups must be accessible to oCIS. This can be achieved either connecting oCIS to the same LDAP server, or by migrating users and groups from the LDAP server that ownCloud Classic is connected to to a different backend for oCIS. The following procedures are necessary for the data migration to be possible. -OC10 Requirements:: +ownCloud Classic Requirements:: + -- In addition to the regular requirements: @@ -294,7 +294,7 @@ sudo -u www-data \ Verify:: + -- -Verify that the OC10 installation is ready for migration. This checks that all enabled users have valid, non-duplicate email addresses: +Verify that the ownCloud Classic installation is ready for migration. This checks that all enabled users have valid, non-duplicate email addresses: [source,bash] ---- @@ -321,7 +321,7 @@ sudo -u www-data \ migrate:to-ocis:migrate:files admin ---- -Each user's home directory contents are migrated into that user's *personal Space* in oCIS. External mounts and received shares are excluded — only files owned by the user in their OC10 home are transferred. +Each user's home directory contents are migrated into that user's *personal Space* in oCIS. External mounts and received shares are excluded — only files owned by the user in their ownCloud Classic home are transferred. The following users are skipped and will not cause the migration to stop: @@ -344,4 +344,4 @@ The same users are skipped as in the file migration step. The following share er * Shares pointing to missing users or groups (that were not migrated). * Link shares that fail due to password restrictions. -For password-protected link shares: the share will be migrated with a new password that does not match the original OC10 password. Users should change the passwords of all their share links after migration. +For password-protected link shares: the share will be migrated with a new password that does not match the original ownCloud Classic password. Users should change the passwords of all their share links after migration. diff --git a/modules/admin_manual/pages/maintenance/upgrading/manual_upgrade.adoc b/modules/admin_manual/pages/maintenance/upgrading/manual_upgrade.adoc index ed9e704ce..c5a33b33b 100644 --- a/modules/admin_manual/pages/maintenance/upgrading/manual_upgrade.adoc +++ b/modules/admin_manual/pages/maintenance/upgrading/manual_upgrade.adoc @@ -83,7 +83,7 @@ If you have made changes in `.user.ini` located at the webroot of ownCloud, you === Download the Latest Release -Download the latest {oc-complete-base-url}/{oc-complete-name}.tar.bz2[ownCloud Server release] to the same location where your previous instance is located, in this example the default directory `/var/www/`. +Download the latest {oc-complete-base-url}/{oc-complete-name}.tar.bz2[ownCloud Classic release] to the same location where your previous instance is located, in this example the default directory `/var/www/`. [source,bash,subs="attributes+"] ---- diff --git a/modules/admin_manual/pages/maintenance/upgrading/upgrade.adoc b/modules/admin_manual/pages/maintenance/upgrading/upgrade.adoc index 555b9f8e8..60e4f40a4 100644 --- a/modules/admin_manual/pages/maintenance/upgrading/upgrade.adoc +++ b/modules/admin_manual/pages/maintenance/upgrading/upgrade.adoc @@ -1,4 +1,4 @@ -= How to Upgrade Your ownCloud Server += How to Upgrade Your ownCloud Classic :toc: right :page-aliases: maintenance/upgrade.adoc, maintenance/upgrading/index.adoc diff --git a/modules/admin_manual/pages/troubleshooting/providing_logs_and_config_files.adoc b/modules/admin_manual/pages/troubleshooting/providing_logs_and_config_files.adoc index 16318b6cb..49dd23ae9 100644 --- a/modules/admin_manual/pages/troubleshooting/providing_logs_and_config_files.adoc +++ b/modules/admin_manual/pages/troubleshooting/providing_logs_and_config_files.adoc @@ -40,11 +40,11 @@ To generate a config report from the command line, run the following command fro {occ-command-example-prefix} configreport:generate > config_report.txt ---- -== ownCloud Server Log File +== ownCloud Classic Log File === Generate via webUI -You can use the webUI to download your ownCloud Server log file. To do so, navigate to: + +You can use the webUI to download your ownCloud Classic log file. To do so, navigate to: + menu:Settings[Admin > General > Log > "Download logfile"]. === Generate via Command Line diff --git a/modules/admin_manual/pages/useful_pages.adoc b/modules/admin_manual/pages/useful_pages.adoc index af5b964ce..d651eae5f 100644 --- a/modules/admin_manual/pages/useful_pages.adoc +++ b/modules/admin_manual/pages/useful_pages.adoc @@ -1,7 +1,7 @@ = Useful Pages :toc: right -:description: When new to ownCloud Server, the following list of useful pages may help getting up and running quickly. +:description: When new to ownCloud Classic, the following list of useful pages may help getting up and running quickly. == Introduction diff --git a/modules/classic_ui/pages/files/desktop_mobile_sync.adoc b/modules/classic_ui/pages/files/desktop_mobile_sync.adoc index abe5b11a2..9eef63ee0 100644 --- a/modules/classic_ui/pages/files/desktop_mobile_sync.adoc +++ b/modules/classic_ui/pages/files/desktop_mobile_sync.adoc @@ -6,7 +6,7 @@ {description} See the download link https://owncloud.com/desktop-app/[ownCloud Sync Client] for Windows, Mac OS X and Linux clients. The ownCloud Desktop Sync Client enables you to connect to your private -ownCloud Server. You can create folders in your home directory, and keep +ownCloud Classic. You can create folders in your home directory, and keep the contents of those folders synced with your ownCloud server. Simply copy a file into the directory and the ownCloud desktop client does the rest. Make a change to the files on one computer, it will flow across diff --git a/modules/classic_ui/pages/index.adoc b/modules/classic_ui/pages/index.adoc index 3d962b1e6..b33a428a3 100644 --- a/modules/classic_ui/pages/index.adoc +++ b/modules/classic_ui/pages/index.adoc @@ -1,5 +1,5 @@ = Introduction -:description: ownCloud is an open source file sync and share software for everyone from individuals operating the free ownCloud Server edition, to large enterprises and service providers operating the ownCloud Enterprise Subscription. +:description: ownCloud is an open source file sync and share software for everyone from individuals operating the free ownCloud Classic edition, to large enterprises and service providers operating the ownCloud Enterprise Subscription. *Welcome to ownCloud: your self-hosted file sync and share solution.* diff --git a/modules/classic_ui/pages/online_collaboration.adoc b/modules/classic_ui/pages/online_collaboration.adoc index 7784f5505..a8697fa59 100644 --- a/modules/classic_ui/pages/online_collaboration.adoc +++ b/modules/classic_ui/pages/online_collaboration.adoc @@ -20,7 +20,7 @@ NOTE: This feature is *not* available in the community edition, or for Public Li ==== How to Use Secure View -image::enterprise/collaboration/secure-view/collabora-online-administration.png[Configure Secure View in ownCloud Server.,align="center"] +image::enterprise/collaboration/secure-view/collabora-online-administration.png[Configure Secure View in ownCloud Classic.,align="center"] To enable Secure View for an existing, or new, share: diff --git a/modules/classic_ui/pages/pim/sync_thunderbird.adoc b/modules/classic_ui/pages/pim/sync_thunderbird.adoc index 4bf69c21c..3b70697c2 100644 --- a/modules/classic_ui/pages/pim/sync_thunderbird.adoc +++ b/modules/classic_ui/pages/pim/sync_thunderbird.adoc @@ -40,7 +40,7 @@ different addressbook is a move operation. If you are worried about losing the contact, save it to a VCF file using ownCloud (Or LDIF using Thunderbird Addressbook) first! Like dragging from the ownCloud Addressbook to the Personal Address Book removes the contact from -ownCloud Server (_deleting it from all the other synchronized +ownCloud Classic (_deleting it from all the other synchronized installations_) and puts it in your Local Machine -only-Address Book. So be careful or you’ll have unintended consequences where you might have intended a copy operation. diff --git a/modules/classic_ui/partials/nav.adoc b/modules/classic_ui/partials/nav.adoc index 57f5c9fef..75337bd87 100644 --- a/modules/classic_ui/partials/nav.adoc +++ b/modules/classic_ui/partials/nav.adoc @@ -1,5 +1,5 @@ // note that the module reference post xref is now a mandatory element -* ownCloud Server UI +* ownCloud Classic UI ** xref:classic_ui:index.adoc[Introduction] ** xref:classic_ui:files/webgui/overview.adoc[The WebUI] *** xref:classic_ui:webinterface.adoc[Web Interface] diff --git a/modules/developer_manual/pages/app/advanced/code_signing.adoc b/modules/developer_manual/pages/app/advanced/code_signing.adoc index b5a4aefd8..64fa065a4 100644 --- a/modules/developer_manual/pages/app/advanced/code_signing.adoc +++ b/modules/developer_manual/pages/app/advanced/code_signing.adoc @@ -141,7 +141,7 @@ The following errors can be encountered when trying to verify a code signature. For information about how to get access to those results please refer to xref:admin_manual:configuration/general_topics/code_signing.adoc#fixing-invalid-code-integrity-messages[the -Issues section of the ownCloud Server Administration manual]. +Issues section of the ownCloud Classic Administration manual]. `INVALID_HASH` diff --git a/modules/developer_manual/pages/app/fundamentals/database.adoc b/modules/developer_manual/pages/app/fundamentals/database.adoc index bb69acf67..42e2d89a8 100644 --- a/modules/developer_manual/pages/app/fundamentals/database.adoc +++ b/modules/developer_manual/pages/app/fundamentals/database.adoc @@ -134,7 +134,7 @@ Therefore we support three kinds of migration steps, these are: * *SQL:* create a list of executable SQL commands. * *Schema:* migration via schema migration operations. -Starting with ownCloud 10, this is the preferred way to perform any kind of migrations and is enabled by default within core. +Starting with ownCloud Classic 10, this is the preferred way to perform any kind of migrations and is enabled by default within core. Any app which wants to use this mechanism has to enable it in appinfo/info.xml, by adding the following: [source,xml] diff --git a/modules/developer_manual/pages/app/fundamentals/info.adoc b/modules/developer_manual/pages/app/fundamentals/info.adoc index b75cf81ee..89f71b2ec 100644 --- a/modules/developer_manual/pages/app/fundamentals/info.adoc +++ b/modules/developer_manual/pages/app/fundamentals/info.adoc @@ -119,7 +119,7 @@ For publishing themes the category tag must be present — _but empty_ — as in *Required*. Provide a short application description (max. 90 chars). This gets displayed below the product title and on the product tiles. It -is mandatory since ownCloud 10.0.0. +is mandatory since ownCloud Classic 10.0.0. == types diff --git a/modules/developer_manual/pages/app/fundamentals/publishing.adoc b/modules/developer_manual/pages/app/fundamentals/publishing.adoc index 47ac528d9..a55b47ece 100644 --- a/modules/developer_manual/pages/app/fundamentals/publishing.adoc +++ b/modules/developer_manual/pages/app/fundamentals/publishing.adoc @@ -287,7 +287,7 @@ code. This does not depend on whether it happens intentionally or not. | The name/title of your app; Max. 50 characters; Provide a concise name so users can identify your app easily; Do not include your developers/company name. | summary -| Provide a short description (max. 90 chars). This gets displayed below the product title and on the product tiles; mandatory since ownCloud 10.0.0. +| Provide a short description (max. 90 chars). This gets displayed below the product title and on the product tiles; mandatory since ownCloud Classic 10.0.0. | description | Max. 4000 characters; Provide all necessary, detailed information about the product. This should contain all user relevant information. Don’t get lost in technical details, focus on the benefits the product offers; Also, use markdown to layout your description. diff --git a/modules/developer_manual/pages/core/theming.adoc b/modules/developer_manual/pages/core/theming.adoc index dc216d3b3..8702881b4 100644 --- a/modules/developer_manual/pages/core/theming.adoc +++ b/modules/developer_manual/pages/core/theming.adoc @@ -8,7 +8,7 @@ Themes can be used to customize the look and feel of any aspect of an ownCloud installation. They can override the default _JavaScript_, _CSS_, _image_, and _template_ files, as well as the _user interface translations_ with custom versions. They can also affect both the web front-end and the ownCloud Desktop client. However, this documentation only covers customizing the web front-end, _so far_. -NOTE: Before ownCloud 10, theming was done via the `config.php` entry `'theme' => ''`. This is deprecated in ownCloud 10. Users who have this entry in their `config.php` should remove it and use a theme app to customize their ownCloud instance instead. +NOTE: Before ownCloud Classic 10, theming was done via the `config.php` entry `'theme' => ''`. This is deprecated in ownCloud Classic 10. Users who have this entry in their `config.php` should remove it and use a theme app to customize their ownCloud instance instead. == Quick Start @@ -177,7 +177,7 @@ And here’s a longer, more complete example: The value of the `id` element needs to be the name of your theme’s folder. We recommend that it always be prefixed with `theme-`. The main reason for doing so, is that it is alphabetically sorted in a terminal when handling app folders. -The `type` element needs to be the same as is listed above, so that ownCloud knows to handle the app as a theme. The dependencies element needs to be present to set the minimum and maximum versions of ownCloud which are supported. If it’s not present, a warning will be displayed in ownCloud 10 and an error will be thrown in the upcoming ownCloud 11. +The `type` element needs to be the same as is listed above, so that ownCloud knows to handle the app as a theme. The dependencies element needs to be present to set the minimum and maximum versions of ownCloud which are supported. If it’s not present, a warning will be displayed in ownCloud Classic 10 and an error will be thrown in the upcoming ownCloud Classic 11. While the remaining elements are optional, they help when working with the theme in the ownCloud Admin dashboard. Consider filling out as many as possible, as completely as possible. @@ -468,7 +468,7 @@ There are different options for testing themes: === How Can an App Register a Section in the Admin or Personal Section? -As of ownCloud 10.0, apps must register Admin and Personal section settings in `info.xml`. As a result, all calls to +As of ownCloud Classic 10.0, apps must register Admin and Personal section settings in `info.xml`. As a result, all calls to `OC_App::registerPersonal` and `OC_App::registerAdmin` should now be removed. The settings panels of any apps that are still using these calls will now be rendered in the `Additional` section of the dashboard. For each panel an app wishes to register, two things are required: @@ -497,7 +497,7 @@ Next, a controller class which implements the `OCP\Settings\ISettings` interface * getPanel * getPriority -*getSectionID:* This method returns the identifier of the section that this panel should be shown under. ownCloud Server comes with a predefined list of sections which group related settings together; the intention of which is to improve the user experience. This can be found here in +*getSectionID:* This method returns the identifier of the section that this panel should be shown under. ownCloud Classic comes with a predefined list of sections which group related settings together; the intention of which is to improve the user experience. This can be found here in https://github.com/owncloud/core/blob/master/lib/private/Settings/SettingsManager.php#L195[this example]: *getPanel:* This method returns the `OCP\Template` or `OCP\TemplateReponse` which is used to render the panel. The method may also return `null` if the panel should not be shown to the user. diff --git a/modules/developer_manual/pages/index.adoc b/modules/developer_manual/pages/index.adoc index 0fbc5eee4..768927623 100644 --- a/modules/developer_manual/pages/index.adoc +++ b/modules/developer_manual/pages/index.adoc @@ -1,6 +1,6 @@ = Introduction -Welcome to the ownCloud Classic Server Developer Guide. If you want to contribute, please read the +Welcome to the ownCloud Classic Developer Guide. If you want to contribute, please read the https://owncloud.com/contribute/join-the-development/contributor-agreement/[Contributor agreement] first. [width="100%",cols="25%,36%,39%",] diff --git a/modules/developer_manual/pages/testing/acceptance-tests.adoc b/modules/developer_manual/pages/testing/acceptance-tests.adoc index cfbd76e43..b009d067a 100644 --- a/modules/developer_manual/pages/testing/acceptance-tests.adoc +++ b/modules/developer_manual/pages/testing/acceptance-tests.adoc @@ -116,7 +116,7 @@ These can be convenient when a longer list of files is needed, e.g., in a UI tes === Preparing to Run Acceptance Tests -This is a concise guide to running acceptance tests on ownCloud 10. +This is a concise guide to running acceptance tests on ownCloud Classic. Before you can do so, you need to meet a few prerequisites available; these are * ownCloud