mirror of
https://github.com/nextcloud/documentation.git
synced 2026-01-04 02:36:49 +07:00
132 lines
4.4 KiB
ReStructuredText
132 lines
4.4 KiB
ReStructuredText
===============================
|
|
Upgrade Nextcloud From Packages
|
|
===============================
|
|
|
|
|
|
Upgrade Quickstart
|
|
------------------
|
|
|
|
One effective, if unofficial method for keeping Nextcloud current on Linux servers is by configuring
|
|
your system to use Nextcloud via a self contained "Snap" package, A technology allowing users to
|
|
always have the latest version of an "app".
|
|
|
|
That version from Canonical is quite restrictive. It is not aimed at developers or advanced users
|
|
who would want to tune their configuration by installing extra features. It is aimed at end-users
|
|
who want a no-brainer solution. Install it, use it. No need to worry about updating Nextcloud any
|
|
more.
|
|
|
|
It will work for as long as Canonical pushes releases, just like with any other Linux package
|
|
maintained independently of Nextcloud.
|
|
|
|
Installation
|
|
------------
|
|
|
|
**Ubuntu**
|
|
$ sudo snap install nextcloud
|
|
|
|
**All other distros**
|
|
Go to http://snapcraft.io/71
|
|
Type the command to install snapd
|
|
Install Nextcloud $ sudo snap install nextcloud
|
|
|
|
1st login
|
|
---------
|
|
|
|
After a successful install, assuming you and the device on which it was installed are on the
|
|
same network, you should be able to reach the Nextcloud installation by visiting .local in
|
|
your browser. If your hostname is localhost or localhost.localdomain, like on an Ubuntu Base
|
|
device (IoT), nextcloud.local will be used instead.
|
|
|
|
You will be asked to create a password for "admin" and your favourite cloud will be ready
|
|
|
|
**Note**
|
|
|
|
Do not use on IoT devices yet. You probably don't need these instructions anyway if you're
|
|
using Snappy Base 16.04 as it's currently unreleased.
|
|
|
|
|
|
* Make a :doc:`fresh backup <backup>`.
|
|
* Upgrade your Nextcloud snap: sudo snap refresh nextcloud
|
|
* Run :ref:`occ upgrade <command_line_upgrade_label>` (optionally disabling the
|
|
:ref:`migration test
|
|
<migration_test_label>`).
|
|
* :ref:`Apply strong permissions <strong_perms_label>` to your
|
|
Nextcloud directories.
|
|
* Take your Nextcloud server out of :ref:`maintenance mode
|
|
<maintenance_commands_label>`.
|
|
* Re-enable third-party apps.
|
|
|
|
Upgrade Tips
|
|
------------
|
|
|
|
Upgrading Nextcloud from a Snap is just like upgrading any snap package.
|
|
For example:
|
|
|
|
sudo snap refresh nextcloud
|
|
|
|
Your Snap package manager only upgrades the current Nextcloud Snap. Then
|
|
your Nextcloud server is immediately put into maintenance mode. You may not see
|
|
this until you refresh your Nextcloud page.
|
|
|
|
.. figure:: images/upgrade-1.png
|
|
:scale: 75%
|
|
:alt: Nextcloud status screen informing users that it is in maintenance mode.
|
|
|
|
Then use ``occ`` to complete the upgrade. You must run ``occ`` as your HTTP
|
|
user. This example is for Debian/Ubuntu::
|
|
|
|
sudo -u www-data php occ upgrade
|
|
|
|
This example is for CentOS/RHEL/Fedora::
|
|
|
|
sudo -u apache php occ upgrade
|
|
|
|
.. _migration_test_label:
|
|
|
|
Migration Test
|
|
--------------
|
|
|
|
Before completing the upgrade, Nextcloud first runs a simulation by copying all
|
|
database tables to new tables, and then performs the upgrade on them, to ensure
|
|
that the upgrade will complete correctly. The copied tables are deleted after
|
|
the upgrade. This takes twice as much time, which on large installations can be
|
|
many hours, so you can omit this step with the ``--skip-migration-test``
|
|
option, like this example on CentOS::
|
|
|
|
$ sudo -u apache php occ upgrade --skip-migration-test
|
|
|
|
Setting Strong Directory Permissions
|
|
------------------------------------
|
|
|
|
After upgrading, verify that your Nextcloud directory permissions are set
|
|
according to :ref:`strong_perms_label`.
|
|
|
|
If the upgrade fails, then you must try a manual upgrade.
|
|
|
|
|
|
.. _skipped_release_upgrade_label:
|
|
|
|
Upgrading Across Skipped Releases
|
|
---------------------------------
|
|
|
|
It is best to update your Nextcloud installation with every new point release,
|
|
and to never skip any major releases. While this requirement is being worked on,
|
|
for the moment If you have skipped any major releases you can bring your
|
|
Nextcloud current with these steps:
|
|
|
|
If you are using a Snap package:
|
|
sudo snap refresh nextcloud
|
|
|
|
If you did **not** install via a Snap package:
|
|
|
|
#. Upgrade your current version to the latest point release
|
|
#. Upgrade your current version to the next major release
|
|
#. Run upgrade routine
|
|
#. Repeat from step 2 until you reach the last available major release
|
|
|
|
You'll find previous Nextcloud releases in the `Nextcloud Server Changelog
|
|
<https://nextcloud.com/changelog/>`_.
|
|
|
|
If upgrading via your Snap package manager fails, then you must perform a
|
|
:doc:`manual_upgrade`.
|