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

An administrator "update" feature (third party) is available, but will only work on New versions have a LAMP server using ownCloud install defaultsspecific numbering format: x. Once the "one click install" Amahi package has been updated to a new version of ownCloud the package will have to be reinstalledy. z

When reinstalling the ownCloud package make sure all data * x - each year there will be a new release (i.e. 7, 8, 9). This is backed upan '''upgrade'''. To upgrade to the next * y - every calendar quarter there will be a new major version of ownCloud instance(i.e. 8.0 8.1, 8.2), replace the files starting at 0 for quarter one. This is an '''upgrade'''.* z - patch and security intermediate releases are issued as necessary (copyi.e. 8.1.1, 8.1.2) , also known as "point releases". This is an '''update'''.<br/>Refer to the Nextcloud '''[https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule Maintenance and Release Schedule]''' for more information.<br/>__TOC__ The following sections are meant for sites with small to medium installations. If for some reason an update/upgrade fails chances are it will be due to a "PHP timeout" or a software flaw in the new set from ownCloud updater process. "PHP timeouts" can occur on larger installations, refer to the download'''[https://docs. Leave nextcloud.com/ Nextcloud documentation]''' regarding the use of the "config/'''occ'''" directory intact command-line facility (it works well for small to preserve your ownCloud configuration datamedium installations as well. The Should the update/upgrade will happen automatically upon process (this happens from time-to-time) fail due to a software flaw consult the next user login'''[https://help.nextcloud.com/categories/ Nextcloud Forum]''' for possible workarounds or wait a new release of Nextcloud.<br/>===Updating ownCloud/Nextcloud on Amahi=== Use the following steps for updating:

Please remember * Catalog all applications active in the current ownCloud instance. Take special care to check identify the “apache:users” ownership "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 copied current ownCloud instance.* It is recommended that all non-core applications be disabled before updating.* Do backups 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 directoriesownCloud database.* Go to the Amahi Dashboard, Apps => Available, and install the new ownCloud release.* Using a "terminal" connection, "cd" in to the ownCloud directory containing 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, open 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 they there are not setany errors, consult the ownCloud Administrator's guide and possibly the ownCloud Forum.* If the update was successful, use login to the ownCloud "administration" user account as usual.* Navigate to the ownCloud Admin page and confirm the “chown” command new version release number.* Confirm some of the other settings and make appropriate changes (recursivelyfile upload/download sizes, versioning). The upgrade will happen automatically upon * '''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 same, this usually happens with Approved/Experimental applications (there maybe new versions that have to be installed). * Login to a normal user loginaccount and test ownCloud functionality (i.e. sharing) and applications. * If the prior testing was successful have other users test their ownCloud IDs.* The update is now completed.

If reading information ===Upgrading ownCloud/Nextcloud on the ownCloud Community site the terminology for doing "updates" and "upgrades" are termed to be specific activities.Amahi===

Update * It is '''highly''' desirable that your current ownCloud instance is at the latest release number (nothing below release 8.0.0 will upgrade) before the next major version release. This is important as there may have been some important meta data fixes (or other fixes) that the new major release is dependent on. If you skip this step the upgrade for ownCloud may have some problems at a future time. The following sub-steps use an upgrade from ownCloud 8.0.7 to bring 8.1.1 as an example.* Catalog all applications active in the current ownCloud instance . Take special care to its latest point 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.* Do backups of the ownCloud database, binaries and stored files.* Go to the Amahi Dashboard, Apps => Installed, eand uninstall the current ownCloud instance. This will remove the ownCloud binaries and ownCloud database.* Go to the Amahi Dashboard, Apps => Available, and install the new ownCloud release.* The following sub-steps must be done for ownCloud releases from version 8.g0 and beyond. Refer to the ''"ownCloud 48.0and Future Updates/Upgrades on Amahi"'' section on this page for more information.* Using a "terminal" connection, "cd" in to the ownCloud directory containing 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. Remember that this restore '''should be''' from the last major point release (i.e.6 → 48.0.7) versus the new major release (i.e. 8. To 1.1) that will be the upgrade (not update an ). '''DO NOT''' restore the ownCloud installation manually, follow those steps:applications as many may not be compatible with the new release.

• Do a backup.• Unpack * Navigate to the release tarball in the owncloud ownCloud "config" directory, i.e. copy all new files into the ownCloud installation.:• Make sure that the file permissions are correct.• With the next page request the update procedures will run. cd /var/hda/web-apps/owncloud8/html/config/

Upgrade is $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 bring 7.<br/> When required, say an ownCloud instance upgrade from 6 to a new major release7, ereferences with "owncloud6" in this file must be changed to "owncloud7".g'''DO NOT''' change the "version". ownCloud 4The changes can be made with a text editor or the following handy Linux command.0The command looks through the "restored" config.php file in the new ownCloud 7 → 4upgrade instance, for occurrences of owncloud6 and changes them to owncloud7.5.0 sed -i 's/owncloud6/owncloud7/g' /var/hda/web-apps/owncloud7/html/config/config. Always do backups anyway.To upgrade ownCloud, follow those steps:php

• Make sure that you ran the latest point release of the major ownCloud version, e.g. 4.0.x in the 4.5.x series. If not, update to that version first (see above).• Do a backup.• Deactivate all third party applications.• Delete everything from your ownCloud installation directory, except data and ::The "config.• Unpack the release tarball in the owncloud directory (or copy the files thereto).• Make sure that the file permissions are correct.• With the next page request the update procedures will run.• If you had 3rd party applications, check if they provide versions compatible with the new release. If so, install and enable them, update procedures will run if needed.php" would have been changed as follows:

Applications will need ===ownCloud 8.0/Nextcloud and Future Updates/Upgrades on Amahi===In order to be "restored" from backups or re-installedallow multiple instances of different version releases of ownCloud on the same Amahi server naming changes to the main ownCloud application directory and database names have been implemented.

Like a lot software in the Open Source world when there is a new version release (* The ownCloud upgrades/updates)database user ID, password, any "plug-and name have changed in" or "optional" software components written by a "third party author" may not work as expected with the new releasesame manner. It takes time for the third party authors Before updating or upgrading changes will have to update their software components be made to work with the new releaseownCloud "config.php" configuration file before proceeding further.

<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/>