mirror of
https://github.com/nextcloud/documentation.git
synced 2026-01-03 02:09:45 +07:00
Update section Manual Upgrade Procedure
I changed the order of steps to perform the manually upgrade. The third party applications have to be disabled first. After putting the the server in maintenance mode it isn't possible to disable the apps. At second I have adjusted the enumeration.
This commit is contained in:
@@ -150,7 +150,12 @@ If the upgrade fails, then you must try a manual upgrade.
|
||||
Manual Upgrade Procedure
|
||||
------------------------
|
||||
|
||||
Start by putting your server in maintenance mode. This prevents new logins,
|
||||
If you are upgrading to a major release, for example from 7.0.5 to
|
||||
8.0, you must review all third party applications (not core apps), for
|
||||
compatibility with your new ownCloud version. Then disable all of them
|
||||
before starting the upgrade.
|
||||
|
||||
Next putting 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 happening. There are two ways to do this, and the preferred method
|
||||
is to use the ``occ`` command, which you must run as your HTTP user. This example
|
||||
@@ -163,19 +168,15 @@ Please see :doc:`../configuration_server/occ_command` to learn more about ``occ`
|
||||
The other way is by entering your ``config.php`` file and changing
|
||||
``'maintenance' => false,`` to ``'maintenance' => true,``.
|
||||
|
||||
1. If you are upgrading to a major release, for example from 7.0.5 to
|
||||
8.0, you must review all third party applications (not core apps), for
|
||||
compatibility with your new ownCloud version. Then disable all of them
|
||||
before starting the upgrade.
|
||||
2. Back up your existing ownCloud Server database, data directory, and
|
||||
1. Back up your existing ownCloud Server database, data directory, and
|
||||
``config.php`` file. (See :doc:`backup`.)
|
||||
3. Download and unpack the latest ownCloud Server release (Archive file) from
|
||||
2. Download and unpack the latest ownCloud Server release (Archive file) from
|
||||
`owncloud.org/install/
|
||||
<https://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/``
|
||||
4. Stop your web server.
|
||||
3. Stop your web server.
|
||||
|
||||
Apache 2 is the recommended server for ownCloud (see :doc:`../release_notes`
|
||||
for recommended setups and supported platforms.)
|
||||
@@ -195,22 +196,22 @@ for recommended setups and supported platforms.)
|
||||
| openSUSE 12.3 and up | ``systemctl stop apache2`` |
|
||||
+-----------------------+-----------------------------------------+
|
||||
|
||||
5. Rename or move your current ownCloud directory (named ``owncloud/`` if
|
||||
4. Rename or move your current ownCloud directory (named ``owncloud/`` if
|
||||
installed using defaults) to another location.
|
||||
|
||||
6. Unpack your new tarball::
|
||||
5. Unpack your new tarball::
|
||||
|
||||
tar xjf owncloud-latest.tar.bz2
|
||||
|
||||
7. This creates a new ``owncloud/`` directory populated with your new server
|
||||
6. 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`` .
|
||||
|
||||
8. Copy and paste the ``config.php`` file from your old version of
|
||||
7. Copy and paste the ``config.php`` file from your old version of
|
||||
ownCloud to your new ownCloud version.
|
||||
|
||||
9. If you keep your ``data/`` directory in your ``owncloud/`` directory, copy
|
||||
8. 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
|
||||
@@ -219,7 +220,7 @@ for recommended setups and supported platforms.)
|
||||
.. note:: We recommend storing your ``data/`` directory in a location other
|
||||
than your ``owncloud/`` directory.
|
||||
|
||||
10. Restart your web server.
|
||||
9. Restart your web server.
|
||||
|
||||
+-----------------------+-----------------------------------------+
|
||||
| Operating System | Command (as root) |
|
||||
@@ -236,7 +237,7 @@ for recommended setups and supported platforms.)
|
||||
| openSUSE 12.3 and up | ``systemctl start apache2`` |
|
||||
+-----------------------+-----------------------------------------+
|
||||
|
||||
11. Now you should be able to open a Web browser to your ownCloud server and
|
||||
10. Now you should be able to open a Web browser to your ownCloud server and
|
||||
log in as usual. You have a couple more steps to go: You should see a
|
||||
**Start Update** screen, just like in the **Upgrading With Your Linux
|
||||
Package Manager** section, above. Review the prerequisites, and if you have
|
||||
@@ -251,7 +252,7 @@ for recommended setups and supported platforms.)
|
||||
.. note:: The ``occ`` command does not download ownCloud updates. You must first download
|
||||
and install the updated code (steps 1-3), and then ``occ`` performs the final upgrade steps.
|
||||
|
||||
13. The upgrade operation takes a few minutes, depending on the size of your
|
||||
11. The upgrade operation takes a few minutes, depending on the size of your
|
||||
installation. When it is finished you will see a success message, or an
|
||||
error message that will tell where it went wrong.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user