ownCloud does not have a feature for automatically or for manually initiating '''NOTE:''' With the installation introduction of new Nextcloud it has not been determined how version releases. An administrator initiated "update" feature is "enabled" by default, but release numbering will only work in a "traditional" LAMP server environment using ownCloud install defaults. Moving to a new release is achieved by installing a newly updated "one click install" Amahi package. Installing a new ownCloud release manually is also possible but can introduce security risks due to manual configuration changes. Reinstalling a new Amahi package is a safer practice than a manual installbe managed.

When there is a new Starting from the ownCloud version 8.0 release, any third party applications written by new releases are issued in a "third party authortime based" may not work as expected with a new releaseschedule. It takes time for third party authors Please be aware due to update their applications to work with testing and software changes a new ownCloud release. Some third party applications schedule can be "restored" from backups or re-installed from the ownCloud applications store successfully for a new ownCloud version releasechanged suddenly.

When moving to New versions have a new ownCloud version release the '''[httpspecific numbering format://owncloudx.org/ ownCloud Community ]''' has defined two activities, "updates" and "upgrades", as specific implementation activitiesy.z

* x - each year there will be a new release (i.e. 7, 8, 9). This is an '''Update:upgrade''' Bring an ownCloud instance to .* y - every calendar quarter there will be a new "point release" major version (ownCloud 6i.e. 8.08.5 => 61, 8.2), starting at 0for quarter one.6This is an '''upgrade'''.* z - patch and security intermediate releases are issued as necessary (i.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 ownCloud updater process. "PHP timeouts" can occur on larger installations, refer to the '''Upgrade[https: //docs.nextcloud.com/ Nextcloud documentation]''' Bring an ownCloud instance to a new regarding the use of the "major release'''occ'''" command-line facility (ownCloud 6it works well for small to medium installations as well.0Should the update/upgrade process (this happens from time-to-time) fail due to a software flaw consult the '''[https://help.6 => 7nextcloud.0.3)com/categories/ Nextcloud Forum]''' for possible workarounds or wait a new release of Nextcloud.

__TOC__===Updating ownCloud /Nextcloud on Amahi===

Use the following steps for updating ownCloud:

* Catalogue Catalog all applications active in the current ownCloud instance. Take special care to identify the "core" applications that were activated and third party Approved/Experimental applications that were installed. There is no guarantee that third party non-core applications will work on a new ownCloud release.

* Login 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 there are any errors, consult the ownCloud Administrator's guide and possibly the ownCloud Forum.* If the update was successful, login to the ownCloud "adminadministration" ID user account as usual.

* Navigate to the Apps page.* Compare the list of third party party that were used in the previous ownCloud instance with the third party applications available in the newly installed release.* If all the third party applications match then restore the applications from backups.* If there is no match for the third party applications; activate the Enable required "core" and Approved/Experimental applications needed"one-at-a-time", enable the third party applications neededtesting each application. Please remember applications Stop at any behaviour that is not available will take time for the third party authors same, this usually happens with Approved/Experimental applications (there maybe new versions that have to update for the new release versionbe installed). * Login to a normal user ID account and test ownCloud functionality (i.e. sharing) and applications.

===Upgrading ownCloud /Nextcloud on Amahi===

Use the following steps for upgrading ownCloud:

* It is '''extremelyhighly''' important 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 8.1.1 as an example.* Catalogue Catalog all applications active in the current ownCloud instance. Take special care to identify the "core" applications that were activated and third party Approved/Experimental applications that were installed. There is no guarantee that non-core applications will work on a new ownCloud release.

cd /var/hda/web-apps/owncloudowncloudx/html - where "x" is an ownCloud major release number* Restore the ownCloud "config.php" directory file from backups. Remember that this restore '''must should be''' from the last major point release (i.e. 68.0.67) versus the new major release (i.e. 78.01.31) that will be the upgrade (not update).* The following sub-steps must be done for ownCloud releases from version 6.0.5 and beyond. Refer to the ''"ownCloud 7.0 and Future Updates/Upgrades on Amahi"'DO NOT''' section on this page for more information. The following sub-steps use an upgrade from restore the ownCloud 6.0.6 to 7.0.3 applications as an examplemany may not be compatible with the new release.

::* Navigate to the ownCloud "config " directory: cd /var/hda/web-apps/owncloud7owncloud8/html/config/

'datadirectory' => '/var/hda/files/owncloud6owncloud8/data',

'version' => '68.0.6.17', 'dbname' => 'owncloud6owncloud8',

'dbuser' => 'owncloud6owncloud8', 'dbpassword' => 'owncloud6owncloud8',

----'''NOTE::All '''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.

::The "config.php" will be would have been changed as follows:

* Using an Internet Browser navigate to ownCloud, the upgrade will now begin,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. Follow When completed it should redirect to the ownCloud login screen. If there are any instructions given by errors, consult the ownCloud Administrator's guide and possibly the ownCloud upgrade processForum.* If the upgrade was successful, login to the ownCloud "adminadministration" ID user account as usual.

* Activate Enable "core" applications that were used in the previous ownCloud instance"one-at-time". Testing each after enabling.* Compare Enable/Install any additional Approved/Experimental applications available from the list of third party applications new release that were used in the previous prior ownCloud instance with the third party applications available in the newly installed release.* Enable the third party applications that are available. Please remember applications not available will take time for the third party authors to update for the new release versionTesting each after enabling.* Login to a normal user ID account and test ownCloud functionality (i.e. sharing) and applications.

===ownCloud 8.0 /Nextcloud and Future Updates/Upgrades on Amahi===

* Starting with ownCloud 8.0, any-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-any major version upgrades will be supportedprovide basic functionality. Prior Most "core" applications have now been moved to the ownCloud appStore. ===Upgrading ownCloud 8.02.1 to Nextcloud 10.x on Amahi===About June 1, 2016 one of the founders, some developers, it and some staff broke away from the ownCloud organization. The result was necessary to upgrade one major version at the creation of a time (i.e"fork" product based on ownCloud 9, called "Nextcloud". Nextcloud 9 was introduced as a "plug-in" replacement for ownCloud 5 -> 6 -> 7 -> 8)9. With ownCloud 8However, it will be possible 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 8scratch 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 to 8.3 or 1. So the question, can we skip a major upgrade step (Nextcloud 9.1 directly0.54)? Well, kind of, with some issues, it is possible. This section will help you with that.

* Minor releases (versions that increase the third digit in the number) are planned by The '''supported upgrade path''' should be for example; ''ownCloud for roughly each month8. This means that once a month a minor release is "potentially" created for each supported version2. Amahi will not necessarily provide all minor releases (i1 => Nextcloud 9.e0. 854 => Nextcloud 10.0.1, ''. This works flawlessly. The steps that follow are not '''not guaranteed''' to work for every new upgrade instance of Nextcloud 10. ownCloud 8.02.2) unless a new minor 1 is the earliest release passes Amahi Tester certificationtested. In If the past we upgrade steps do not work for a new upgrade instance you will have experienced very buggy minor releases they disable main core functionality of ownCloudto start with a complete new installation. The Nextcloud Community will not help with issues where an upgrade step was skipped.

* Starting with ownCloud 8'''NOTE: ''' The section for '''[https://wiki.amahi.0, on upgrade, most applications are disabled, only certain basic applications are left enabled (Files, Pictures)org/index. The php/Backup_and_Recovery_of_ownCloud Backup and Recovery of ownCloud Communityr /Nextcloud ]''' has "slimmed" down their installation package to provide basic functionality. Most "core" applications have now been moved to the ownCloud appStore.updated, please read carefully!

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