[Pkg-owncloud-commits] [owncloud-doc] 158/227: Added warning that enterprise customers should not use updater app

David Prévot taffit at moszumanska.debian.org
Sat Oct 11 17:20:45 UTC 2014


This is an automated email from the git hooks/post-receive script.

taffit pushed a commit to branch master
in repository owncloud-doc.

commit b046e6812753a864185e5fcd3c51d6744752d726
Author: Carla Schroder <carla at owncloud.com>
Date:   Tue Sep 23 09:48:54 2014 -0700

    Added warning that enterprise customers should not use updater app
---
 admin_manual/maintenance/update.rst | 37 ++++++++++++++++++++++++++-----------
 1 file changed, 26 insertions(+), 11 deletions(-)

diff --git a/admin_manual/maintenance/update.rst b/admin_manual/maintenance/update.rst
index fa9161f..c773b32 100644
--- a/admin_manual/maintenance/update.rst
+++ b/admin_manual/maintenance/update.rst
@@ -1,6 +1,10 @@
 Updating ownCloud with the Updater App
 ======================================
 
+The Updater app automates many of the steps of updating an ownCloud installation 
+to the next point release. The Updater app should be enabled in your ownCloud 
+instance by default, which you can easily confirm by looking on your Apps page.
+
 Updating and upgrading your ownCloud installation are two different tasks. 
 Updating means updating to the next point release, which is indicated 
 by third digit of the version number. For example, 4.5.1, 5.0.17, 6.0.4 and 
@@ -11,17 +15,28 @@ Major releases are indicated by the first and second digits. So 4.5.0, 5.0.0,
 6.0.0, and 7.0.0 are major releases. The Updater app is not for upgrades; 
 please see :doc:`upgrade` for instructions on upgrading to a major release.
 
-.. note:: If you installed ownCloud from your Linux distribution repositories 
-   using your package manager, then it is best to update/upgrade ownCloud using 
-   your package manager and staying in sync with your distro updates, rather 
-   than using the Updater app or upgrading manually. You should still 
-   maintain regular backups (see :doc:`backup`), and make a backup before every 
-   update/upgrade. 
-
-The Updater app automates many of the steps of updating an ownCloud installation 
-to the next point release. The Updater app should be enabled in your ownCloud 
-instance by default, which you can easily confirm by looking on your Apps page.
-
+If you installed ownCloud from your Linux distribution repositories using your 
+package manager, then it is best to update/upgrade ownCloud using your package 
+manager and staying in sync with your distro updates, rather than using the 
+Updater app or upgrading manually. You should still maintain regular backups 
+(see :doc:`backup`), and make a backup before every update/upgrade. 
+
+.. note:: Enterprise customers, and anyone with a large ownCloud installation 
+   should not use the Updater app. The Updater app is better for smaller 
+   installations that have less data and fewer users, and for admins who do not 
+   have shell access, for example on a hosted server. Larger installations 
+   should update ownCloud with their Linux package managers or manually 
+   upgrade, and then complete the update with the ``occ`` command, which is 
+   in the ``owncloud`` directory. Run ``occ --help`` to see command options.
+   
+   For large installations there is a higher risk of PHP timeouts. There are 
+   two places where PHP timeouts are likely to happen: 
+   1. When the updater app makes a backup, and you have a large number of files 
+   to backup. 
+   2. After the Updater app is done and you click the "Start upgrade" button 
+   in the Web UI; the migration/repair process may take too long on large 
+   numbers of files.
+   
 The Updater app performs these operations:
 
 * Creates a ``backup`` directory under your ownCloud data directory

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-owncloud/owncloud-doc.git



More information about the Pkg-owncloud-commits mailing list