Starting from the ownCloud does not have a feature for automatically or for manually initiating the installation of 8.0 release, new version releasesare issued in a "time based" schedule. Moving Please be aware due to testing and software changes a new release is usually achieved by installing a newly updated Amahi package but installing the new ownCloud release manually is also possible. Reinstalling a new Amahi package is a safer practice than a manual installschedule can be changed suddenly.

Like New versions have a lot software in the Open Source world when there is a new ownCloud version release, any third party applications written by a "third party author" may not work as expected with a new release. It takes time for the third party authors to update their applications to work with a new ownCloud releasespecific numbering format: x. Some third party applications can be "restored" from backups or re-installed from the ownCloud applications store successfully for a new ownCloud version releasey.z

For Amahi, ownCloud must 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 reinstalled due to a "PHP timeout" or a software flaw in order the ownCloud updater process. "PHP timeouts" can occur on larger installations, refer to move the '''[https://docs.nextcloud.com/ Nextcloud documentation]''' regarding the use of the "'''occ'''" command-line facility (it works well for small to medium installations as well. Should the update/upgrade process (this happens from time-to-time) fail due to a software flaw consult the '''[https://help.nextcloud.com/categories/ Nextcloud Forum]''' for possible workarounds or wait a new version releaseof Nextcloud. Additionally, installed third party applications may have to be reinstalled.<br/>===Updating ownCloud/Nextcloud on Amahi===

Use the following steps for Amahiupdating:

* Catalogue 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.

* It is recommended that all non-core applications be disabled before updating.* Do backups of the ownCloud database , binaries and stored files.* Download Go to the Amahi Dashboard, Apps => Installed, and uninstall the current ownCloud instance. This will remove the new tarball (tarownCloud binaries and ownCloud database.bz2) file for * 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 known directory location"terminal" connection and using the command-line '''OR''' an Amahi MySQL application restore the ownCloud database from backups. * Extract 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 tarball 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 copy in possibly the ownCloud Forum.* If the update was successful, login to the ownCloud "administration" user account as usual.* Navigate to the ownCloud Admin page and confirm the 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!* Enable required "core" and Approved/Experimental applications "one-at-a-time", testing each application directory. Stop at any behaviour that is not the 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 is now completed.

tar -xjf path===Upgrading ownCloud/to/downloaded/owncloud-x.x.x.tar.bz2 cp -r owncloud /var/hda/web-apps/owncloud/html <Nextcloud on Amahi=== this is a recursive copy command

$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 referencing information on 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 ownCloud Community site following handy Linux command. The command looks through the terminology for doing "updatesrestored" config.php file in the new ownCloud 7 upgrade instance, for occurrences of owncloud6 and "upgrades" are termed changes them to be specific activitiesowncloud7. sed -i 's/owncloud6/owncloud7/g' /var/hda/web-apps/owncloud7/html/config/config.php

Update $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 "terminal" connection 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,something similar will display:::[[File:oc-updater-8.png‎]]::This is the ownCloud "updater" process, it will do attempt to bring an 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 upgrade was successful, login to its latest point the ownCloud "administration" user account as usual.* Navigate to 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 4instance "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.5Testing each after enabling.5 => 4* Login to a normal user account and test ownCloud functionality (i.5e.5sharing)and applications. * If the prior testing was successful have other users test their ownCloud IDs.* The upgrade is now completed.

To update an ===ownCloud installation manually, follow those steps:8.0/Nextcloud and Future Updates/Upgrades on Amahi===In order to allow 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.

# Do a backup.# Unpack * The location where the actual ownCloud application is stored has changed to "/var/hda/web-apps/owncloudx/html" (where "x" is the major release tarball in the owncloud directory, inumber).e. copy all new files into the For example for ownCloud installationrelease version 7.# Make sure that the file permissions are correct0.# With 3 the next page request the update procedures will rundirectory is named owncloud7.

Upgrade is * You may want to bring an consider changing your ownCloud instance to a new major release, edata file directory name for the same naming convention.gProvided you used the name owncloud as part of the data directory name. ownCloud 4.0.7 → 4.5.0. Always do backups anyway.To upgrade ownCloud, follow those steps:

• Make sure that * If you use automated backup and recovery software you ran the latest point release of the major may have to reload and reconfigure your ownCloud version, e.g. 4.0.x in data and backup system configuration before the 4next backup set is taken.5.x series. If not, update Some backup systems allow you to that version first (see above).• Do a backup.• Deactivate all third party applications.• Delete everything from your change the ownCloud installation directorynames (data, except data and ownCloud config.• Unpack the release tarball ,php location) in the owncloud directory existing backup sets (or copy the files theretorsnapshot).• 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.

An administrator * Starting with ownCloud 8.0, on upgrade, most applications are disabled, only certain "updatecore" feature applications are left enabled (third partyFiles, Pictures) is available, but will only work in a . The ownCloud Community has "traditionalslimmed" LAMP server environment using ownCloud install defaultsdown their installation package to provide basic functionality. Once the Most "one click installcore" Amahi package has applications have now been updated moved to a new version of the ownCloud the package will have to be reinstalledappStore.

When reinstalling ===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 package make sure all data is backed uporganization. To upgrade to The result was the next version creation of a "fork" product based on ownCloud 9, called "Nextcloud". Nextcloud 9 was introduced as a "plug-in" replacement for ownCloud instance9. However, replace the files (copy) with the new set due to severe bugs inherited from ownCloud the downloadupdate/upgrade process did not function correctly. Later releases of Nextcloud 9. Leave 0.54 and 10.0.1 repaired the "config/" directory intact process. Unfortunately due to preserve your the broken process many Amahi users are still using earlier stable releases of ownCloud configuration . 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 dataand sharing configurations. Amahi has decided to go straight to Nextcloud 10. The 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 happen automatically upon the next user loginhelp you with that.

Please remember The '''supported upgrade path''' should be for example; ''ownCloud 8.2.1 => Nextcloud 9.0.54 => Nextcloud 10.0.1''. This works flawlessly. The steps that follow are not '''not guaranteed''' to check work for every new upgrade instance of Nextcloud 10. ownCloud 8.2.1 is the “apache:users” ownership on earliest release tested. If the copied files and directoriesupgrade steps do not work for a new upgrade instance you will have to start with a complete new installation. If they are The Nextcloud Community will not set, use the “chown” command (recursively)help with issues where an upgrade step was skipped.

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