mirror of
https://github.com/nextcloud/documentation.git
synced 2026-01-03 02:09:45 +07:00
ownCloud > Nextcloud
Replaced ownCloud references with Nextcloud Replaced suggestion to use OBS packages with Snap package (as this page is about using packages) I left occ as occ for the moment until we presumably eventually replace it with ncc when we later allow breaking OC compatibility (or symlink occ to ncc) Removed reference to disabling third party apps, as I believe NC does this automatically now, but left the reference to re-enabling them as we don't yet do that (if I remember correctly) I left the reference to the ownCloud status screen as a reminder to update the screenshot to nextcloud.
This commit is contained in:
Bugsbane
@@ -1,63 +1,72 @@
|
||||
==============================
|
||||
Upgrade ownCloud From Packages
|
||||
Upgrade Nextcloud From Packages
|
||||
==============================
|
||||
|
||||
.. note:: Starting with ownCloud 8.2 the Linux package repositories have
|
||||
changed, and **you must configure your system to use these new
|
||||
repositories** to install or upgrade ownCloud 8.2+. The new repositories are
|
||||
at our `Open Build Service`_.
|
||||
|
||||
Upgrade Quickstart
|
||||
------------------
|
||||
|
||||
The best method for keeping ownCloud current on Linux servers is by configuring
|
||||
your system to use ownCloud's `Open Build Service`_ repository. Then stay
|
||||
current by using your Linux package manager to install fresh ownCloud packages.
|
||||
After installing upgraded packages you must run a few more steps to complete
|
||||
the
|
||||
upgrade. These are the basic steps to upgrading ownCloud:
|
||||
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.
|
||||
|
||||
|
||||
* :doc:`Disable <../installation/apps_management_installation>` all third-party
|
||||
apps.
|
||||
* Make a :doc:`fresh backup <backup>`.
|
||||
* Upgrade your ownCloud packages.
|
||||
* 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
|
||||
ownCloud directories.
|
||||
* Take your ownCloud server out of :ref:`maintenance mode
|
||||
Nextcloud directories.
|
||||
* Take your Nextcloud server out of :ref:`maintenance mode
|
||||
<maintenance_commands_label>`.
|
||||
* Re-enable third-party apps.
|
||||
|
||||
Upgrade Tips
|
||||
------------
|
||||
|
||||
Upgrading ownCloud from our `Open Build Service`_ repository is just like any
|
||||
normal Linux upgrade. For example, on Debian or Ubuntu Linux this is the
|
||||
standard system upgrade command::
|
||||
Upgrading Nextcloud from a Snap is just like upgrading any snap package.
|
||||
For example:
|
||||
|
||||
apt-get update && apt-get upgrade
|
||||
sudo snap refresh nextcloud
|
||||
|
||||
Or you can upgrade just ownCloud with this command::
|
||||
|
||||
apt-get update && apt-get install owncloud
|
||||
|
||||
On Fedora, CentOS, and Red Hat Linux use ``yum`` to see all available updates::
|
||||
|
||||
yum check-update
|
||||
|
||||
You can apply all available updates with this command::
|
||||
|
||||
yum update
|
||||
|
||||
Or update only ownCloud::
|
||||
|
||||
yum update owncloud
|
||||
|
||||
Your Linux package manager only downloads the current ownCloud packages. Then
|
||||
Your Snap package manager only upgrades the current Nextcloud Snap. Then
|
||||
your ownCloud server is immediately put into maintenance mode. You may not see
|
||||
this until you refresh your ownCloud page.
|
||||
this until you refresh your Nextcloud page.
|
||||
|
||||
.. figure:: images/upgrade-1.png
|
||||
:scale: 75%
|
||||
@@ -77,7 +86,7 @@ This example is for CentOS/RHEL/Fedora::
|
||||
Migration Test
|
||||
--------------
|
||||
|
||||
Before completing the upgrade, ownCloud first runs a simulation by copying all
|
||||
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
|
||||
@@ -89,32 +98,34 @@ option, like this example on CentOS::
|
||||
Setting Strong Directory Permissions
|
||||
------------------------------------
|
||||
|
||||
After upgrading, verify that your ownCloud directory permissions are set
|
||||
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.
|
||||
|
||||
.. _Open Build Service:
|
||||
https://download.owncloud.org/download/repositories/stable/owncloud/
|
||||
|
||||
.. _skipped_release_upgrade_label:
|
||||
|
||||
Upgrading Across Skipped Releases
|
||||
---------------------------------
|
||||
|
||||
It is best to update your ownCloud installation with every new point release,
|
||||
and to never skip any major releases. If you have skipped any major releases you
|
||||
can bring your ownCloud current with these steps:
|
||||
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:
|
||||
|
||||
#. Add the repository of your current version
|
||||
#. Upgrade your current version to the latest point release
|
||||
#. Add the repo of the next major release
|
||||
#. Upgrade your current version to the next major release
|
||||
#. Run upgrade routine
|
||||
#. Repeat from step 3 until you reach the last available major release
|
||||
#. Repeat from step 2 until you reach the last available major release
|
||||
|
||||
You'll find previous ownCloud releases in the `ownCloud Server Changelog
|
||||
<https://owncloud.org/changelog/>`_.
|
||||
You'll find previous Nextcloud releases in the `Nextcloud Server Changelog
|
||||
<https://nextcloud.com/changelog/>`_.
|
||||
|
||||
If upgrading via your package manager fails, then you must perform a
|
||||
If upgrading via your Snap package manager fails, then you must perform a
|
||||
:doc:`manual_upgrade`.
|
||||
|
||||
Reference in New Issue
Block a user