As stated before there is no "automatic upgrade" facility for Starting from the ownCloud 8.0 release, new versions of ownCloud or for third party releases are issued in a "plug-in/optionaltime based" schedule. Please be aware due to testing and software componentschanges a schedule can be changed suddenly.

When referencing information on the ownCloud Community site the terminology * x - each year there will be a new release (i.e. 7, 8, 9). This is an '''upgrade'''.* y - every calendar quarter there will be a new major version (i.e. 8.0 8.1, 8.2), starting at 0 for doing "updates" quarter one. This is an '''upgrade'''.* z - patch and security intermediate releases are issued as necessary (i.e. 8.1.1, 8.1.2), also known as "upgradespoint releases" are termed . This is an '''update'''.<br/>Refer to be specific activitiesthe Nextcloud '''[https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule Maintenance and Release Schedule]''' for more information.<br/>__TOC__

Update is to bring an ownCloud instance to its latest point release, e.g. ownCloud 4.0.6 → 4.0.7. To update an ownCloud installation manually, follow those Use the following stepsfor updating:

• * Catalog all applications active in the current ownCloud instance. Take special care to identify the "core" applications that were activated and Approved/Experimental applications that were installed. There is no guarantee that non-core applications will work on a new ownCloud release.* Review and document all ownCloud sharing techniques used in the current ownCloud instance.* It is recommended that all non-core applications be disabled before updating.* Do a backupbackups of the ownCloud database, binaries and stored files.* Go to the Amahi Dashboard, Apps => Installed, and uninstall the current ownCloud instance. This will remove the ownCloud binaries and ownCloud database.• Unpack * Go to the Amahi Dashboard, Apps => Available, and install the new ownCloud release tarball .* Using a "terminal" connection, "cd" in to the owncloud ownCloud directorycontaining the binaries. cd /var/hda/web-apps/owncloudx/html - where "x" is an ownCloud major release number* Restore the ownCloud "config.php" file from backups.* Restore the ownCloud apps directory from backups.* Using a "terminal" connection and using the command-line '''OR''' an Amahi MySQL application restore the ownCloud database from backups.* Using a web browser, iopen ownCloud and something similar will display:::[[File:oc-updater-8.png‎]]::This is the ownCloud "updater" process, it will do attempt to do the final update steps to the new ownCloud instance. When completed it should redirect to the ownCloud login screen. If there are any errors, consult the ownCloud Administrator's guide and possibly the ownCloud Forum.e* If the update was successful, login to the ownCloud "administration" user account as usual. copy all new files into * Navigate to the ownCloud installationAdmin page and confirm the new version release number.• Make sure that * Confirm some of the other settings and make appropriate changes (file permissions are correctupload/download sizes, versioning).• With * '''DO NOT''' turn the system over to users yet!* Enable required "core" and Approved/Experimental applications "one-at-a-time", testing each application. Stop at any behaviour that is not the next page request same, this usually happens with Approved/Experimental applications (there maybe new versions that have to be installed). * Login to a normal user account and test ownCloud functionality (i.e. sharing) and applications. * If the prior testing was successful have other users test their ownCloud IDs.* The update procedures will runis now completed.

Upgrade is to bring an ownCloud instance to a new major release, e.g. ownCloud 4.0.7 → 4.5.0. Always do backups anyway.To upgrade ownCloud, follow those Use the following stepsfor upgrading:

• Make sure * It is '''highly''' desirable that you ran your current ownCloud instance is at the latest point release of number (nothing below release 8.0.0 will upgrade) before the next major ownCloud version, erelease. This is important as there may have been some important meta data fixes (or other fixes) that the new major release is dependent on.gIf you skip this step the upgrade for ownCloud may have some problems at a future time. 4The following sub-steps use an upgrade from ownCloud 8.0.x 7 to 8.1.1 as an example.* Catalog all applications active in the 4.5.x seriescurrent ownCloud instance. If not, update Take special care to identify the "core" applications that were activated and Approved/Experimental applications that version first (see above)were installed.• Do There is no guarantee that non-core applications will work on a backupnew ownCloud release.• Deactivate * Review and document all third party applicationsownCloud sharing techniques used in the current ownCloud instance.• Delete everything from your * Do backups of the ownCloud installation directorydatabase, binaries and stored files.* Go to the Amahi Dashboard, Apps => Installed, except data and configuninstall the current ownCloud instance. This will remove the ownCloud binaries and ownCloud database.• Unpack * Go to the Amahi Dashboard, Apps => Available, and install the new ownCloud release tarball .* The following sub-steps must be done for ownCloud releases from version 8.0 and beyond. Refer to the ''"ownCloud 8.0 and Future Updates/Upgrades on Amahi"'' section on this page for more information.* Using a "terminal" connection, "cd" in to the owncloud ownCloud directory (or copy containing the files thereto)binaries.• Make sure cd /var/hda/web-apps/owncloudx/html - where "x" is an ownCloud major release number* Restore the ownCloud "config.php" file from backups. Remember that this restore '''should be''' from the file permissions are correctlast major point release (i.e. 8.0.• With 7) versus the next page request new major release (i.e. 8.1.1) that will be the upgrade (not update procedures will run).• If you had 3rd party '''DO NOT''' restore the ownCloud applications, check if they provide versions as many may not be compatible with the new release. If so, install and enable them, update procedures will run if needed.

Applications will need to be ::The restored "config"restoreddirectory contains a file, " from backups or re-installedconfig.php" as follows:

Please Note $CONFIG = array ( 'instanceid' => 'xxx', 'passwordsalt' => 'xxxx', 'datadirectory' => '/var/hda/files/owncloud8/data', 'dbtype' => 'mysql', 'version' => '8.0.7', 'dbname' => 'owncloud8', 'dbhost' => 'localhost', 'dbtableprefix' => 'oc_', 'dbuser' => 'owncloud8', 'dbpassword' => 'owncloud8', 'installed' => true, 'theme' => '', 'maintenance' => false, );----'''NOTE:'''The following old example shows a major release change from 6 to 7.<br/> When required, say an upgrade from 6 to 7, references with "owncloud6" in this file must be changed to "owncloud7". '''DO NOT''' change the "version". The changes can be made with a text editor or the following handy Linux command. The command looks through the "restored" config.php file in the new ownCloud 7 upgrade instance, for occurrences of owncloud6 and changes them to owncloud7. sed -i 's/owncloud6/owncloud7/g' /var/hda/web-apps/owncloud7/html/config/config.php

Like a lot software in the Open Source world when there is a new version release (ownCloud upgrades/updates), any ::The "plug-in" or "optionalconfig.php" software components written by a "third party author" may not work would have been changed as expected with the new release. It takes time for the third party authors to update their software components to work with the new release.follows:

An administrator $CONFIG = array ( 'instanceid' => 'xxx', 'passwordsalt' => 'xxxx', 'datadirectory' => '/var/hda/files/owncloud7/data', 'dbtype' => 'mysql', 'version' => '6.0.6.1', 'dbname' => 'owncloud7', 'dbhost' => 'localhost', 'dbtableprefix' => 'oc_', 'dbuser' => 'owncloud7', 'dbpassword' => 'owncloud7', 'installed' => true, 'theme' => '', 'maintenance' => false, );----* Using a "updateterminal" feature (third party) is availableconnection and using the command-line '''OR''' an Amahi MySQL application, restore the ownCloud database from backups.* Using an Internet Browser navigate to ownCloud, the upgrade will now begin, but something similar will only work in a display:::[[File:oc-updater-8.png‎]]::This is the ownCloud "traditionalupdater" LAMP server environment using process, it will do attempt to do the final update steps to the new ownCloud instance. When completed it should redirect to the ownCloud login screen. If there are any errors, consult the ownCloud Administrator's guide and possibly the ownCloud install defaultsForum. Once * If the upgrade was successful, login to the ownCloud "one click installadministration" Amahi package has been updated user account as usual.* Navigate to a the Admin page and confirm new version release number.* Confirm some of the other settings and make appropriate changes (file upload/download sizes, versioning).* '''DO NOT''' turn the system over to users yet!* Navigate to the Apps page.* Enable "core" applications that were used in the previous ownCloud instance "one-at-time". Testing each after enabling.* Enable/Install any additional Approved/Experimental applications available from the new release that were used in the prior ownCloud instance. Testing each after enabling.* Login to a normal user account and test ownCloud functionality (i.e. sharing) and applications. * If the package will prior testing was successful have to be reinstalledother users test their ownCloud IDs.* The upgrade is now completed.

When reinstalling the ===ownCloud package make sure all data is backed up8. To upgrade 0/Nextcloud and Future Updates/Upgrades on Amahi===In order to the next allow multiple instances of different version releases of ownCloud instance, replace on the files (copy) with same Amahi server naming changes to the new set from the download. Leave the "config/" main ownCloud application directory intact to preserve your ownCloud configuration data. The upgrade will happen automatically upon the next user loginand database names have been implemented.

Please remember * The location where the actual ownCloud application is stored has changed to check "/var/hda/web-apps/owncloudx/html" (where "x" is the “apache:users” ownership on the copied files and directoriesmajor release number). For example for ownCloud release version 7. If they are not set, use the “chown” command (recursively)0. The upgrade will happen automatically upon 3 the next user logindirectory is named owncloud7.

<br>* You may want to consider changing your ownCloud data file directory name for the same naming convention. Provided you used the name owncloud as part of the data directory name. __TOC__* If you use automated backup and recovery software you may have to reload and reconfigure your ownCloud data and backup system configuration before the next backup set is taken. Some backup systems allow you to change the ownCloud directory names (data, ownCloud config,php location) in the existing backup sets (rsnapshot). * Starting with ownCloud 8.0, on upgrade, most applications are disabled, only certain "core" applications are left enabled (Files, Pictures). The ownCloud Community has "slimmed" down their installation package to provide basic functionality. Most "core" applications have now been moved to the ownCloud appStore. ===Upgrading ownCloud 8.2.1 to Nextcloud 10.x on Amahi===About June 1, 2016 one of the founders, some developers, and some staff broke away from the ownCloud organization. The result was the creation of a "fork" product based on ownCloud 9, called "Nextcloud". Nextcloud 9 was introduced as a "plug-in" replacement for ownCloud 9. However, due to severe bugs inherited from ownCloud the update/upgrade process did not function correctly. Later releases of Nextcloud 9.0.54 and 10.0.1 repaired the process. Unfortunately due to the broken process many Amahi users are still using earlier stable releases of ownCloud. Implementing Nextcloud would have resulted in users starting from scratch with new installations. This is a problem for instances that have big collections of stored data and sharing configurations. Amahi has decided to go straight to Nextcloud 10.0.1. So the question, can we skip a major upgrade step (Nextcloud 9.0.54)? Well, kind of, with some issues, it is possible. This section will help you with that.

# Backup the ownCloud 8.2.1 (not guaranteed to work for anything earlier) instance to be upgrade, including the database.# Rename the old owncloud code directory in “/var/www/html/”, to say “xowncloud”.# Download and extract “Nextcloud 10.0.x” to a "Downloads" or other known location.# Rename the “nextcloud” binaries directory to “owncloud”.# Copy the downloaded binaries (owncloud) directory over to the "/var/www/html/" location.# Go to the copied "owncloud" directory under /var/www/html/, find PHP files; "version.php" and "index.php". '''Copy''' them to a known location, they will be required downstream in the upgrade.# In “owncloud” directory, in the “version.php” file.# Find the line containing "$OC_VersionCanBeUpgradedFrom".# Change the entry to: $OC_VersionCanBeUpgradedFrom = array(8,2,1); '''<span style="color:#FF0000"><== DO NOT TRY THIS FOR VERSIONS PRIOR TO V8.2.1, IT MOST LIKELY WILL FAIL.</span>'''# Drop and create the database instance.# Perform the usual recommended upgrade steps (from backups??): ## Restore the old "config.php". ## Restore the database. ## Set permissions and ownership to binaries directory structure.# Now do the usual upgrade process (i.e. via the browser GUI). The upgrade "should" complete successfully. '''DO NOT''' login to Nextcloud yet.# Copy the original “index.php” and “version.php” files from the "known" location in to the “owncloud” directory, replacing the existing copies (this will overwrite the modified version.php).# After the copying of the PHP files, restart the Apache or reboot the server.# Login to Nextcloud as the “administration user” and go to the “Admin” application. A scanning operation will begin in the “Security & setup warnings” section. # After a period of time a warning message will appear in “red” stating that a “Code Integrity check...” failure has occurred.# On the red line for this failure, "click" on the "Rescan" link. This will force a new Nextcloud scan. After the new scan the code check failure should disappear.# Test the new instance. On the surface most things will upgrade correctly. ::*Sharing and data configurations tested worked "mostly".::*Some applications may not upgrade correctly, usually disabling/enabling each application should fix the issue. ::*If using “External Storage Support”, there maybe a double entry for the same items. Delete the second one.<br/>