diff --git a/CLAUDE.md b/CLAUDE.md index 564d4c516..1b52122f6 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -4,7 +4,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co ## Overview -This is an [Antora](https://antora.org/)-based documentation site for ownCloud Server. Documentation is written in AsciiDoc and built into a static HTML site. This repo is not built standalone in production — it is built as part of the main [owncloud/docs](https://github.com/owncloud/docs) repository, but can be built locally for preview. +This is an [Antora](https://antora.org/)-based documentation site for ownCloud Classic. Documentation is written in AsciiDoc and built into a static HTML site. This repo is not built standalone in production — it is built as part of the main [owncloud/docs](https://github.com/owncloud/docs) repository, but can be built locally for preview. ## Commands diff --git a/README.md b/README.md index 459337461..928e78e3d 100644 --- a/README.md +++ b/README.md @@ -1,10 +1,10 @@ -# ownCloud Server Documentation +# ownCloud Classic Documentation [![License](https://img.shields.io/badge/License-AGPL--3.0-blue.svg)](LICENSE) [![ownCloud OSPO](https://img.shields.io/badge/OSPO-ownCloud-blue)](https://kiteworks.com/opensource) -Antora-based documentation component for ownCloud Server (OC10). This repository contains the AsciiDoc source files for server administration, user management, configuration, and maintenance documentation, published to [doc.owncloud.com](https://doc.owncloud.com). +Antora-based documentation component for ownCloud Classic (OC10). This repository contains the AsciiDoc source files for server administration, user management, configuration, and maintenance documentation, published to [doc.owncloud.com](https://doc.owncloud.com). ## Getting Started @@ -26,7 +26,7 @@ This generates a standalone preview at `http://localhost:8080`. For the full sit ## Part of ownCloud Documentation -This is a content component for the [ownCloud docs](https://github.com/owncloud/docs) Antora build. The ownCloud Server source code lives at [owncloud/core](https://github.com/owncloud/core). Published documentation is available at [doc.owncloud.com](https://doc.owncloud.com). +This is a content component for the [ownCloud docs](https://github.com/owncloud/docs) Antora build. The ownCloud Classic source code lives at [owncloud/core](https://github.com/owncloud/core). Published documentation is available at [doc.owncloud.com](https://doc.owncloud.com). ## Community & Support diff --git a/agents.md b/agents.md index e9f765226..39875ef47 100644 --- a/agents.md +++ b/agents.md @@ -1,4 +1,4 @@ -# AI Agent Guidelines for ownCloud Server Documentation +# AI Agent Guidelines for ownCloud Classic Documentation This file provides context for AI coding agents (Claude Code, GitHub Copilot, Cursor, etc.) working in this repository. diff --git a/antora.yml b/antora.yml index 08ec5b826..cb936948a 100644 --- a/antora.yml +++ b/antora.yml @@ -1,5 +1,5 @@ name: server -title: ownCloud Server +title: ownCloud Classic version: next prerelease: true start_page: ROOT:index.adoc 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 e6925f327..3c21316a0 100644 --- a/modules/admin_manual/pages/configuration/integration/splunk.adoc +++ b/modules/admin_manual/pages/configuration/integration/splunk.adoc @@ -67,11 +67,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 90606a835..0f6776b3e 100644 --- a/modules/admin_manual/pages/configuration/server/harden_server.adoc +++ b/modules/admin_manual/pages/configuration/server/harden_server.adoc @@ -6,7 +6,7 @@ go/enable-http-strict-transport-security.adoc == Introduction -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. +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 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 7a93c4ab3..7920f5f2f 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 b2853a46b..2f7d58909 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 28f5730f1..80816e3d1 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 @@ -102,7 +102,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 61b708433..39931e2a0 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,11 +16,11 @@ 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. |=== -When you are performing an update or upgrade on your ownCloud Server (see the Maintenance section of this manual), it is better to use `occ` to perform the database upgrade step, rather than the Web GUI, in order to avoid timeouts. PHP scripts invoked from the Web interface are limited to 3600 seconds. In larger environments this may not be enough, leaving the system in an inconsistent state. After performing all the preliminary steps (see the xref:maintenance/upgrading/upgrade.adoc[Maintenance - Upgrade documentation]) use this command to upgrade your databases, like this example: +When you are performing an update or upgrade on your ownCloud Classic (see the Maintenance section of this manual), it is better to use `occ` to perform the database upgrade step, rather than the Web GUI, in order to avoid timeouts. PHP scripts invoked from the Web interface are limited to 3600 seconds. In larger environments this may not be enough, leaving the system in an inconsistent state. After performing all the preliminary steps (see the xref:maintenance/upgrading/upgrade.adoc[Maintenance - Upgrade documentation]) use this command to upgrade your databases, like this example: [source,docker,subs="attributes+"] ---- 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 cfab773a4..70aa51337 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 @@ -13,7 +13,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,docker,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 2891df0f9..bcffec428 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 @@ -154,7 +154,7 @@ Use `encryption:disable` to disable your encryption module. You must first put y `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/security_setup_warnings.adoc b/modules/admin_manual/pages/configuration/server/security_setup_warnings.adoc index bb34f55aa..fee3584e8 100644 --- a/modules/admin_manual/pages/configuration/server/security_setup_warnings.adoc +++ b/modules/admin_manual/pages/configuration/server/security_setup_warnings.adoc @@ -3,7 +3,7 @@ == Introduction -Your ownCloud Server has a built-in configuration checker, and it reports its findings at the top of your Admin page. These are some of the warnings you might see, and what to do about them. +Your ownCloud Classic has a built-in configuration checker, and it reports its findings at the top of your Admin page. These are some of the warnings you might see, and what to do about them. image:security-setup-warning-complete.png[image] diff --git a/modules/admin_manual/pages/configuration/server/ui-configuration.adoc b/modules/admin_manual/pages/configuration/server/ui-configuration.adoc index 1b338e88a..2a92ec938 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 11f7e8c41..c76d35c46 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. Enable the OpenID Connect App 2. Configure via environment variables @@ -43,7 +43,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. +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 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 0f72a366d..f63324c3b 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=350] -=== 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 559cd91b9..e95e27db1 100644 --- a/modules/admin_manual/pages/configuration/user/oidc/oidc.adoc +++ b/modules/admin_manual/pages/configuration/user/oidc/oidc.adoc @@ -28,7 +28,7 @@ Click on the xref:attachment$/configuration/user/oidc/OAuth-code-flow-sequence-d == 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 @@ -45,11 +45,11 @@ 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 `OpenID Connect` app enabled on ownCloud Server. +* The `OpenID Connect` app enabled on ownCloud Classic. * Set the environment variable: + -- @@ -99,7 +99,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] ---- @@ -246,7 +246,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 19f7e6bd2..2f34b5a04 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=350 + image:configuration/user/oidc/onelogin/onelogin-oidc-sso.png[width=350] -=== 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/enterprise/authentication/kerberos.adoc b/modules/admin_manual/pages/enterprise/authentication/kerberos.adoc index 0d46e5e96..213053990 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. @@ -321,7 +321,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 Run the commands from the server hosting ownCloud, following these steps. Note that you need to provide a Docker Volume to add/manipulate and backup the various Kerberos configuration files. 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 f94c0c3d9..dfd3d2961 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 e55c7851f..84448c10c 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 @@ -291,7 +291,7 @@ NOTE: The capability of the listener depends on the ability of the used SMB/CIFS ==== WND Listener Setup -The WND listener for ownCloud 11 includes two different commands that need to be executed: +The WND listener for ownCloud Classic 11 includes two different commands that need to be executed: * xref:wndlisten[wnd:listen] + Listen to changes and save them in the database. + @@ -569,7 +569,7 @@ smbclient \ kdestroy ---- -=== 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 31833d5e8..d301aae12 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/reporting/metrics.adoc b/modules/admin_manual/pages/enterprise/reporting/metrics.adoc index 262904e69..646e1e21c 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 ac9128b66..aa09f362a 100644 --- a/modules/admin_manual/pages/index.adoc +++ b/modules/admin_manual/pages/index.adoc @@ -1,10 +1,10 @@ = Introduction -Welcome to the ownCloud Classic Server Administration Guide. This guide describes administration tasks for ownCloud, the flexible open source file synchronization and sharing solution. +Welcome to the ownCloud Classic Administration Guide. This guide describes administration tasks for ownCloud, the flexible open source file synchronization and sharing solution. == Installation Changes -IMPORTANT: Unlike previous releases, ownCloud 11 is only available as a Docker image containing the necessary libraries, such as PHP 8. +IMPORTANT: Unlike previous releases, ownCloud Classic 11 is only available as a Docker image containing the necessary libraries, such as PHP 8. == Target Audience diff --git a/modules/admin_manual/pages/installation/deployment_considerations.adoc b/modules/admin_manual/pages/installation/deployment_considerations.adoc index d040494bc..3c6a6a619 100644 --- a/modules/admin_manual/pages/installation/deployment_considerations.adoc +++ b/modules/admin_manual/pages/installation/deployment_considerations.adoc @@ -53,11 +53,11 @@ When primary fails another replica can become primary. However, the increased co === Docker Host -ownCloud Server 11 runs exclusively in Docker containers. The host operating system only needs to provide Docker Engine and Docker Compose. A basic web server (Apache), the required PHP runtime, and the application dependencies are all encapsulated within the ownCloud Docker image. +ownCloud Classic 11 runs exclusively in Docker containers. The host operating system only needs to provide Docker Engine and Docker Compose. A basic web server (Apache), the required PHP runtime, and the application dependencies are all encapsulated within the ownCloud Docker image. === Web Proxy -The Docker image does not handle SSL. Therefore, you must use a proxy in front of this image to add web security and other web-related settings. The embedded web server is pre-configured to serve ownCloud Server 11; further configuration is not possible. +The Docker image does not handle SSL. Therefore, you must use a proxy in front of this image to add web security and other web-related settings. The embedded web server is pre-configured to serve ownCloud Classic 11; further configuration is not possible. === Relational Database diff --git a/modules/admin_manual/pages/installation/deployment_recommendations.adoc b/modules/admin_manual/pages/installation/deployment_recommendations.adoc index 4f61b351e..5760c9db3 100644 --- a/modules/admin_manual/pages/installation/deployment_recommendations.adoc +++ b/modules/admin_manual/pages/installation/deployment_recommendations.adoc @@ -149,7 +149,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 @@ -239,7 +239,7 @@ You may take a look at the NetApp NFS Best Practice and Implementation Guide for ==== 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 @@ -329,7 +329,7 @@ You may take a look at the NetApp NFS Best Practice and Implementation Guide for ==== 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/installing_with_docker.adoc b/modules/admin_manual/pages/installation/installing_with_docker.adoc index fda1d158f..faf39ffbb 100644 --- a/modules/admin_manual/pages/installation/installing_with_docker.adoc +++ b/modules/admin_manual/pages/installation/installing_with_docker.adoc @@ -22,7 +22,7 @@ installation/selinux_configuration.adoc {description} This {dockerhub-url}[official image] is designed to be used in a docker compose setup but can also be used for a quick evaluation. -Starting with ownCloud Server 11, the only supported installation method is a Docker-based installation which includes PHP 8 and Apache. Manual installation on Linux is no longer supported. +Starting with ownCloud Classic 11, the only supported installation method is a Docker-based installation which includes PHP 8 and Apache. Manual installation on Linux is no longer supported. == Database Notes diff --git a/modules/admin_manual/pages/installation/system_requirements.adoc b/modules/admin_manual/pages/installation/system_requirements.adoc index 237d6af68..c485fb219 100644 --- a/modules/admin_manual/pages/installation/system_requirements.adoc +++ b/modules/admin_manual/pages/installation/system_requirements.adoc @@ -1,6 +1,6 @@ = System Requirements :toc: right -:description: Read this documentation for the supported environment for your ownCloud Server. Starting with ownCloud Server 11, only Docker-based installations are supported. +:description: Read this documentation for the supported environment for your ownCloud Classic server. Starting with ownCloud Classic 11, only Docker-based installations are supported. :desktop-system-requirements-url: https://doc.owncloud.com/desktop/ :ios-system-requirements-url: https://doc.owncloud.com/ios-app/ @@ -12,7 +12,7 @@ == Docker Host Requirements -ownCloud Server 11 is exclusively deployed via Docker. The following requirements apply to the Docker host: +ownCloud Classic 11 is exclusively deployed via Docker. The following requirements apply to the Docker host: [width="100%",cols="30%,70%a",options="header"] |=== 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 8a5345d46..ef7355021 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.adoc b/modules/admin_manual/pages/maintenance/migrating.adoc index 9d6923f6d..8f001094c 100644 --- a/modules/admin_manual/pages/maintenance/migrating.adoc +++ b/modules/admin_manual/pages/maintenance/migrating.adoc @@ -10,7 +10,7 @@ The following scenarios are described here: . Migrating to a different host . Migrating to a different domain -. Migrating from ownCloud 10 to ownCloud 11 +. Migrating from ownCloud Classic 10 to ownCloud Classic 11 Note that any database migration is not covered here. @@ -53,7 +53,7 @@ Migration to a different host is easy with Docker. === Domain Migration -As the ownCloud 11 image provides an embedded Apache web server, you need a proxy to handle security and other web-related settings anyway. To migrate or add a domain, two steps are required: +As the ownCloud Classic 11 image provides an embedded Apache web server, you need a proxy to handle security and other web-related settings anyway. To migrate or add a domain, two steps are required: . Update your proxy server settings . Update the ownCloud trusted domain settings @@ -98,24 +98,24 @@ services: ---- -- -=== ownCloud Server Migration +=== ownCloud Classic Migration -This section describes the migration of *ownCloud 10* to *ownCloud 11*, if ownCloud 10 was installed natively. It only focuses on ownCloud but not on any migration of the database! +This section describes the migration of *ownCloud Classic 10* to *ownCloud Classic 11*, if ownCloud Classic 10 was installed natively. It only focuses on ownCloud but not on any migration of the database! -Due to the wide range of installation types, the description focuses on the main steps rather than the details. When using encryption with the ownCloud 10 instance, the openSSL requirements must be met without circumventing retired ciphers. See the ownCloud 10 encryption documentation for more details. +Due to the wide range of installation types, the description focuses on the main steps rather than the details. When using encryption with the ownCloud Classic 10 instance, the openSSL requirements must be met without circumventing retired ciphers. See the ownCloud Classic 10 encryption documentation for more details. -. Enable maintenance mode on ownCloud 10 +. Enable maintenance mode on ownCloud Classic 10 . Create a mount point to bind mount the Docker volume. + For more details see the xref:installation/mount_folder_structure.adoc[Mount Folder Structure] documentation. -. Install ownCloud 11 using a bind mount and down the container. + -This will install/prepare ownCloud 11 in a basic way but it is not configured to your needs. + +. Install ownCloud Classic 11 using a bind mount and down the container. + +This will install/prepare ownCloud Classic 11 in a basic way but it is not configured to your needs. + For details see: xref:installation/installing_with_docker.adoc[Installing With Docker]. . Adapt the compose yaml file to your needs. + Remove any environment variables from the compose file that are no longer relevant, such as those for the database. These settings are now covered by a new configuration file, see below. . Migrate the `data/files` directory into `mount-point/files`. -. Migrate all apps from ownCloud 10 that are NOT part of ownCloud 11 into the `mount-point/apps` directory. + +. Migrate all apps from ownCloud Classic 10 that are NOT part of ownCloud Classic 11 into the `mount-point/apps` directory. + For more details see the xref:installation/apps_management_installation.adoc[Apps Management] documentation. . Make a copy of your existing `config.php` file *with a new name* and remove any setting that addresses the `data` directory and `apps` / `apps-external` directories into the `mount-point/config` directory. + See the important note with regards to the config in the xref:installation/mount_folder_structure.adoc[Mount Folder Structure] documentation. -. Bring up the ownCloud 11 container. +. Bring up the ownCloud Classic 11 container. . Disable maintenance mode. diff --git a/modules/admin_manual/pages/maintenance/migrating_to_ocis.adoc b/modules/admin_manual/pages/maintenance/migrating_to_ocis.adoc index c81ea9faf..48caa528e 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 10 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 10 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 10 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 10 [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 xref:ocis:admin:deployment/services/s-list/idm.adoc[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, the migration of users and groups is di === 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 external 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 external 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 by connecting oCIS to the same LDAP server, or by migrating users and groups from the LDAP server that OC10 uses into a different backend for oCIS. +In general, users and groups must be accessible to oCIS. This can be achieved either by connecting oCIS to the same LDAP server, or by migrating users and groups from the LDAP server that ownCloud Classic uses into 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/upgrade.adoc b/modules/admin_manual/pages/maintenance/upgrading/upgrade.adoc index f071203b5..9b90d6cf1 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 :description: When an update or upgrade is available for your ownCloud server, you will see a notification at the top of your ownCloud Web interface. diff --git a/modules/admin_manual/pages/troubleshooting/general_troubleshooting.adoc b/modules/admin_manual/pages/troubleshooting/general_troubleshooting.adoc index 5647b44cb..9d335a4d9 100644 --- a/modules/admin_manual/pages/troubleshooting/general_troubleshooting.adoc +++ b/modules/admin_manual/pages/troubleshooting/general_troubleshooting.adoc @@ -241,7 +241,7 @@ Misconfigured Web server:: == OAuth2 -=== ownCloud Apps Cannot Connect to the ownCloud Server +=== ownCloud Apps Cannot Connect to the ownCloud Classic If ownCloud clients cannot connect to your ownCloud server, check to see if PROPFIND requests receive `HTTP/1.1 401 Unauthorized` responses. If this is happening, more than likely your web-proxy server configuration is stripping out the https://tools.ietf.org/html/rfc6750[bearer authorization header]. 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 10f0fef2b..f49664aa0 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-docker} 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 d4758f427..7a28c9868 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 3e5fbaa4b..62f13cf3b 100644 --- a/modules/developer_manual/pages/app/fundamentals/database.adoc +++ b/modules/developer_manual/pages/app/fundamentals/database.adoc @@ -127,7 +127,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 7ee08790a..71d8642db 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 61e603dcd..88c4bb707 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\TemplateResponse` 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 8fbaeff44..2221c1bcf 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 10. Before you can do so, you need to meet a few prerequisites available; these are * ownCloud