diff --git a/admin_manual/installation/linux_installation.rst b/admin_manual/installation/linux_installation.rst index a79444f12..e0a5abb36 100644 --- a/admin_manual/installation/linux_installation.rst +++ b/admin_manual/installation/linux_installation.rst @@ -19,9 +19,6 @@ installation. (see :doc:`installation_wizard`). .. note:: Do not move the folders provided by these packages after the installation, as this will break updates. -.. _Open Build Service: - https://download.owncloud.org/download/repositories/8.2/owncloud/ - Installing ownCloud Enterprise Subscription ------------------------------------------- @@ -74,3 +71,8 @@ want to use CalDAV or CardDAV clients make sure you have configured the correct **Note for MySQL/MariaDB environments**: Please refer to :ref:`db-binlog-label` on how to correctly configure your environment if you have binary logging enabled. + + +.. _Open Build Service: + https://download.owncloud.org/download/repositories/9.0/owncloud/ + \ No newline at end of file diff --git a/admin_manual/maintenance/manual_upgrade.rst b/admin_manual/maintenance/manual_upgrade.rst index e311632d2..99d1ee797 100644 --- a/admin_manual/maintenance/manual_upgrade.rst +++ b/admin_manual/maintenance/manual_upgrade.rst @@ -2,7 +2,7 @@ Manual ownCloud Upgrade ======================= -Always start by making a fresh backup & disabling all 3rd party apps. +Always start by making a fresh backup and disabling all 3rd party apps. Put your server in maintenance mode. This prevents new logins, locks the sessions of logged-in users, and displays a status screen so users know what is @@ -19,34 +19,31 @@ The other way is by entering your ``config.php`` file and changing ``config.php`` file. (See :doc:`backup`.) 2. Download and unpack the latest ownCloud Server release (Archive file) from `owncloud.org/install/`_ into an empty directory outside - of your current installation. For example, if your current ownCloud is - installed in ``/var/www/owncloud/`` you could create a new directory called - ``/var/www/owncloud2/`` + of your current installation. .. note:: To unpack your new tarball, run: - tar xjf owncloud-latest.tar.bz2 + tar xjf owncloud-[version].tar.bz2 .. note:: Enterprise users must download their new ownCloud archives from their accounts on ``_ 3. Stop your Web server. -4. Rename or move your current ownCloud directory (named ``owncloud/`` if - installed using defaults) to another location. +4. Rename your current ownCloud directory, for example ``owncloud-old``. -5. This creates a new ``owncloud/`` directory populated with your new server - files. Copy this directory and its contents to the original location of your - old server, for example ``/var/www/``, so that once again you have - ``/var/www/owncloud`` . +5. Unpacking the new archive creates a new ``owncloud`` directory populated + with your new server files. Copy this directory and its contents to the + original location of your old server, for example ``/var/www/``, so that + once again you have ``/var/www/owncloud``. -6. Copy and paste the ``config.php`` file from your old version of - ownCloud to your new ownCloud version. +6. Copy the ``config.php`` file from your old ownCloud directory to your new + ownCloud directory. 7. If you keep your ``data/`` directory in your ``owncloud/`` directory, copy - it from your old version of ownCloud to the ``owncloud/`` directory of - your new ownCloud version. If you keep it outside of ``owncloud/`` then - you don't have to do anything with it, because its location is configured in - your original ``config.php``, and none of the upgrade steps touch it. + it from your old version of ownCloud to your new ``owncloud/``. If you keep + it outside of ``owncloud/`` then you don't have to do anything with it, + because its location is configured in your original ``config.php``, and + none of the upgrade steps touch it. 8. If you are using 3rd party applications, look in your new ``owncloud/apps/`` directory to see if they are there. If not, copy them from your old ``apps/``