Changes

From Amahi Wiki
Jump to: navigation, search

Upgrading ownCloud to New Version Releases (view source)

Revision as of 19:46, 15 November 2016

10,494 bytes added ,  19:46, 15 November 2016
→‎Upgrading ownCloud 8.2.1 to Nextcloud 10.x on Amahi
{{WorkInProgress}}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 "update" feature (third party) is available, but release numbering will only work in a "traditional" LAMP server environment using ownCloud install defaults. Moving to a new release is usually 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. 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 the third party authors to update their applications Please be aware due 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/features/ 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 major version (i.e. 8.0 8.1, 8.2), starting at 0 for 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 "point releasereleases" (ownCloud 4.5This is an '''update'''.5 =<br/> 4Refer to the Nextcloud '''[https://github.5.6)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 4it works well for small to medium installations as well.5Should the update/upgrade process (this happens from time-to-time) fail due to a software flaw consult the '''[https://help.6 => 5nextcloud.0.0)com/categories/ Nextcloud Forum]''' for possible workarounds or wait a new release of Nextcloud.
<br/>
__TOC__===Updating ownCloud/Nextcloud on Amahi===
'''Please NoteUse the following steps for updating:''' Information following is based on Fedora installations.
===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 backups of the ownCloud database, binaries and stored files.* Go to the AmahiDashboard, Apps => Installed, and 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.* 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 there are any errors, consult the ownCloud Administrator's guide and 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. 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.
For ===Upgrading ownCloud/Nextcloud on Amahi, ownCloud must be reinstalled in order to move to a new version release. Additionally, installed third party applications may have to be reinstalled.===
Use the following steps for package reinstallationupgrading:
* Catalogue 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 8.1.1 as an example.* 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.
* 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 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.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 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. 8.0.7) versus the new major release (i.e. 8.1.1) that will be the upgrade (not update). '''DO NOT''' restore the ownCloud applications as many may not be compatible with the new release.
restore * Navigate to the ownCloud "config from backups" directory: restore cd /var/hda/web-apps from backups restore database from backups login to admin as usual confirm new version number test other user logins test owncloud apps test owncloud sharing/owncloud8/html/config/
::The restored "config" directory contains a file, "config.php" as follows:
To update $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 installation manually7 upgrade instance, follow those steps:for occurrences of owncloud6 and changes them to owncloud7. sed -i 's/owncloud6/owncloud7/g' /var/hda/web-apps/owncloud7/html/config/config.php
* Do a backup.* Download the new tarball (tar.bz2) file for the new ownCloud release in to a known directory location. * Extract the tarball and copy in to the ownCloud application directory::The "config.php" would have been changed as follows:
<blockquote $CONFIG = array ( 'instanceid' => 'xxx', 'passwordsalt' => 'xxxx', 'datadirectory' =>{{Code|tar -xjf path'/var/hda/tofiles/downloadedowncloud7/ownclouddata', 'dbtype' => 'mysql', 'version' => '6.0.6.1', 'dbname' => 'owncloud7', 'dbhost' => 'localhost', 'dbtableprefix' => 'oc_', 'dbuser' => 'owncloud7', 'dbpassword' => 'owncloud7', 'installed' => true, 'theme' => '', 'maintenance' => false, );----x* Using a "terminal" connection and using the command-line '''OR''' an Amahi MySQL application, restore the ownCloud database from backups.x* Using an Internet Browser navigate to ownCloud, the upgrade will now begin,something similar will display:::[[File:oc-updater-8.xpng‎]]::This is the ownCloud "updater" process, it will do attempt to do the final update steps to the new ownCloud instance.tarWhen 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 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.bz2cp * Enable "core" applications that were used in the previous ownCloud instance "one-r owncloud /var/hda/webat-appstime". Testing each after enabling.* Enable/owncloudInstall any additional Approved/html}} Experimental applications available from the new release that were used in the prior ownCloud instance. Testing each after enabling.</blockquote>* 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 upgrade is now completed.
* Using the "cd" command go to "===ownCloud 8.0/varNextcloud and Future Updates/hda/web-apps/owncloud/html/".Upgrades on Amahi===* Change In order to allow multiple instances of different version releases of ownCloud on the ownership and permissions of same Amahi server naming changes to the contents of this main ownCloud application directory (Ubuntu ownerships are "www-data:www-data")and database names have been implemented.
<blockquote>{{Code|​chown -vR apache:users *chmod The location where the actual ownCloud application is stored has changed to "/var/hda/web-vR 775 *}} <apps/owncloudx/blockquote>html" (where "x" is the major release number). For example for ownCloud release version 7.0.3 the directory is named owncloud7.
* The ownCloud database user ID, password, and name have changed in the same manner. Before updating or upgrading changes will have to be made to the ownCloud "config.php" configuration file before proceeding further.
* 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.
Always do backups anyway* 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.To upgrade Some backup systems allow you to change the ownCloud directory names (data, ownCloudconfig, follow those steps:php location) in the existing backup sets (rsnapshot).
• Make sure that you ran the latest point release of the major * Starting with ownCloud version, e.g. 48.0.x in the 4.5.x series. If not, update to that version first on upgrade, most applications are disabled, only certain "core" applications are left enabled (see aboveFiles, Pictures).• Do a backup.• Deactivate all third party applications.• Delete everything from your The ownCloud Community has "slimmed" down their installation directory, except data and 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 runpackage to provide basic functionality.• If you had 3rd party Most "core" applications, check if they provide versions compatible with have now been moved to the new release. If so, install and enable them, update procedures will run if neededownCloud appStore.
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.
===Upgrading '''NOTE: ''' The section for '''[https://wiki.amahi.org/index.php/Backup_and_Recovery_of_ownCloud Backup and Recovery of ownCloud on Amahi===/Nextcloud ]''' has been 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/>
----
[[OwnCloud|Main ownCloud Page]]
Retrieved from "https://wiki.amahi.org/index.php/Special:MobileDiff/67682...106126"