Difference between revisions of "Upgrading ownCloud to New Version Releases"
Line 32: | Line 32: | ||
* Login to the admin ID as usual. | * Login to the admin ID as usual. | ||
* Navigate to Settings => Admin and the confirm new version release number. | * Navigate to Settings => Admin and the confirm new version release number. | ||
− | * '''DO NOT''' turn system over to users yet! | + | * '''DO NOT''' turn the system over to users yet! |
go to apps and check current apps list to see if all apps used in prior ownCloud instance are available | go to apps and check current apps list to see if all apps used in prior ownCloud instance are available |
Revision as of 02:34, 4 February 2013
Work In Progress | |
---|---|
This article is currently undergoing major expansion or restructuring. You are welcome to assist by editing it as well. If this article has not been edited in several days, please remove this template. |
ownCloud does not have a feature for automatically or for manually initiating the installation of new version releases. An administrator "update" feature (third party) is available, but 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 install.
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 third party authors to update their applications to work with a new ownCloud release. Some third party applications can be "restored" from backups or re-installed from the ownCloud applications store successfully for a new ownCloud version release.
When moving to a new ownCloud version release the ownCloud Community has defined two activities, "updates" and "upgrades", as specific implementation activities.
- Update: Bring an ownCloud instance to a new "point release" (ownCloud 4.5.5 => 4.5.6).
- Upgrade: Bring an ownCloud instance to a new "major release" (ownCloud 4.5.6 => 5.0.0).
Please Note:
Information following is based on Fedora installations.
Updating ownCloud on Amahi
Use the following steps for updating ownCloud:
- Catalogue all applications active in the current ownCloud instance. Take special care to identify the "core" applications were activated and third party applications were installed.
- 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.
- Using a "terminal" connection, "cd" in to the ownCloud directory containing the binaries and delete the ownCloud "config" directory.
bash code cd /var/hda/web-apps/owncloud/html rm -fr config
- Restore the ownCloud "config" from backups.
- Using a "terminal" connection and using the command-line OR an Amahi MySQL application restore the ownCloud database from backups.
- Login to the admin ID as usual.
- Navigate to Settings => Admin and the confirm new version release number.
- DO NOT turn the system over to users yet!
go to apps and check current apps list to see if all apps used in prior ownCloud instance are available of the new relase. if apps are available then restore apps from backup else activate "core" applications install third party applications end if
- Login to a normal user ID 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.
Upgrading ownCloud on Amahi
Use the following steps for upgrading ownCloud:
- Catalogue all applications active in the current ownCloud instance. Take special care to identify which "core" applications were activated and which third party applications were installed.
- Review and document all ownCloud sharing techniques used in the current ownCloud instance.
- Do backups of the ownCloud database 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.
• 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 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.