Difference between revisions of "Upgrading ownCloud to New Version Releases"
From Amahi Wiki
m |
|||
| Line 19: | Line 19: | ||
Use the following steps for updating ownCloud: | 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. | + | * Catalogue all applications active in the current ownCloud instance. Take special care to identify the "core" applications that were activated and third party applications that were installed. |
* Review and document all ownCloud sharing techniques used in the current ownCloud instance. | * Review and document all ownCloud sharing techniques used in the current ownCloud instance. | ||
* Do backups of the ownCloud database, binaries and stored files. | * Do backups of the ownCloud database, binaries and stored files. | ||
| Line 28: | Line 28: | ||
rm -fr config}} | rm -fr config}} | ||
</blockquote> | </blockquote> | ||
| − | * Restore the ownCloud "config" from backups. | + | * Restore the ownCloud "config" 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 "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. | * Login to the admin ID as usual. | ||
| Line 35: | Line 35: | ||
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 | ||
| − | of the new | + | of the new release. |
if apps are available then | if apps are available then | ||
restore apps from backup | restore apps from backup | ||
| Line 51: | Line 51: | ||
Use the following steps for upgrading ownCloud: | Use the following steps for upgrading ownCloud: | ||
| − | * Catalogue all applications active in the current ownCloud instance. Take special care to identify | + | * Catalogue all applications active in the current ownCloud instance. Take special care to identify the "core" applications that were activated and third party applications that were installed. |
* Review and document all ownCloud sharing techniques used in the current ownCloud instance. | * Review and document all ownCloud sharing techniques used in the current ownCloud instance. | ||
| − | * Do backups of the ownCloud database and stored files. | + | * Deactivate all third party applications ('''not''' the "core" applications). |
| + | * 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 => 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. | * 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. | |
| − | + | <blockquote>{{Code|cd /var/hda/web-apps/owncloud/html | |
| − | + | rm -fr config}} | |
| − | + | </blockquote> | |
| − | + | * Restore the ownCloud "config" directory 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! | |
| − | + | * Navigate to Settings => Apps. | |
| − | * The | + | * Activate "core" applications that were used in the previous ownCloud instance. |
| − | + | * Compare the list of third party applications that were used in the previous 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 version. | ||
| + | * 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 upgrade is now completed. | ||
<br> | <br> | ||
---- | ---- | ||
Revision as of 02:19, 5 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 that were activated and third party applications that 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" directory 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 release. 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 the "core" applications that were activated and third party applications that were installed.
- Review and document all ownCloud sharing techniques used in the current ownCloud instance.
- Deactivate all third party applications (not the "core" applications).
- 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" directory 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!
- Navigate to Settings => Apps.
- Activate "core" applications that were used in the previous ownCloud instance.
- Compare the list of third party applications that were used in the previous 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 version.
- 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 upgrade is now completed.
