Difference between revisions of "Upgrading ownCloud to New Version Releases"
m |
m |
||
| Line 3: | Line 3: | ||
As stated before there is no "automatic upgrade" facility for new versions of ownCloud or for "plug-in/optional" third party software components. | As stated before there is no "automatic upgrade" facility for new versions of ownCloud or for "plug-in/optional" third party software components. | ||
| − | + | Update vs Upgrade | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | When referencing information on the ownCloud Community site the terminology for doing "updates" and "upgrades" are termed to be specific activities. | |
Update | Update | ||
| Line 40: | Line 36: | ||
Like a lot software in the Open Source world when there is a new version release (ownCloud upgrades/updates), any "plug-in" or "optional" software components written by a "third party author" may not work as expected with the new release. It takes time for the third party authors to update their software components to work with the new release. | Like a lot software in the Open Source world when there is a new version release (ownCloud upgrades/updates), any "plug-in" or "optional" software components written by a "third party author" may not work as expected with the new release. It takes time for the third party authors to update their software components to work with the new release. | ||
| + | |||
| + | An administrator "update" feature (third party) is available, but will only work in a "traditional" LAMP server environment using ownCloud install defaults. Once the "one click install" Amahi package has been updated to a new version of ownCloud the package will have to be reinstalled. | ||
| + | |||
| + | When reinstalling the ownCloud package make sure all data is backed up. To upgrade to the next version of ownCloud instance, replace the files (copy) with the new set from the download. Leave the "config/" directory intact to preserve your ownCloud configuration data. The upgrade will happen automatically upon the next user login. | ||
| + | |||
| + | Please remember to check the “apache:users” ownership on the copied files and directories. If they are not set, use the “chown” command (recursively). The upgrade will happen automatically upon the next user login. | ||
| + | |||
<br> | <br> | ||
Revision as of 19:49, 25 January 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. |
As stated before there is no "automatic upgrade" facility for new versions of ownCloud or for "plug-in/optional" third party software components.
Update vs Upgrade
When referencing information on the ownCloud Community site the terminology for doing "updates" and "upgrades" are termed to be specific activities.
Update
Update is to bring an ownCloud instance to its latest point release, e.g. ownCloud 4.0.6 → 4.0.7. To update an ownCloud installation manually, follow those steps:
• Do a backup. • Unpack the release tarball in the owncloud 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.
Upgrade
Upgrade is to bring an ownCloud instance to a new major release, e.g. ownCloud 4.0.7 → 4.5.0. Always do backups anyway.To upgrade ownCloud, follow those steps:
• 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.
Application Release Changes
Applications will need to be "restored" from backups or re-installed.
Please Note:
Like a lot software in the Open Source world when there is a new version release (ownCloud upgrades/updates), any "plug-in" or "optional" software components written by a "third party author" may not work as expected with the new release. It takes time for the third party authors to update their software components to work with the new release.
An administrator "update" feature (third party) is available, but will only work in a "traditional" LAMP server environment using ownCloud install defaults. Once the "one click install" Amahi package has been updated to a new version of ownCloud the package will have to be reinstalled.
When reinstalling the ownCloud package make sure all data is backed up. To upgrade to the next version of ownCloud instance, replace the files (copy) with the new set from the download. Leave the "config/" directory intact to preserve your ownCloud configuration data. The upgrade will happen automatically upon the next user login.
Please remember to check the “apache:users” ownership on the copied files and directories. If they are not set, use the “chown” command (recursively). The upgrade will happen automatically upon the next user login.
