Upgrading the OpenACS files

Index: openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html,v diff -u -r1.27.2.2 -r1.27.2.3 --- openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html 28 Sep 2015 07:54:29 -0000 1.27.2.2 +++ openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html 4 Oct 2015 13:36:55 -0000 1.27.2.3 @@ -1,5 +1,5 @@ -Upgrading the OpenACS files

Prev	Chapter 5. Upgrading	Next

Upgrading the OpenACS files

Chosing a Method to Upgrade your Files

OpenACS is distributed in many different ways: +Upgrading the OpenACS files

Prev	Chapter 5. Upgrading	Next

Upgrading the OpenACS files

Chosing a Method to Upgrade your Files

OpenACS is distributed in many different ways:

as a collection of files
as one big tarball
via CVS
via automatic download from within the APM (package manager)

Upgrades work by first changing the file system (via any @@ -11,7 +11,7 @@ describes whether or not you need to be upgrading using this page or not: the section called “Upgrading an OpenACS 5.0.0 or greater installation” -

Methods of upgrading OpenACS files

Upgrading files for a site which is not in a CVS repository. Unpack the tarball into a new directory and copy its +

Methods of upgrading OpenACS files

Upgrading files for a site which is not in a CVS repository. Unpack the tarball into a new directory and copy its contents on top of your working directory. Or just 'install software', select remote repository, and upgrade your files from there.

[root root]# su - $OPENACS_SERVICE_NAME
@@ -32,7 +32,7 @@
         with the latest OpenACS version, without overriding your own
         local customizations. 
This diagram explains the basic idea. However, the
         labels are incorrect. Step 1(a) has been removed, and Step
-        1(b) should be labelled Step 1.
Figure 5.2. Upgrading a local CVS repository

Step 0: Set up a working CVS checkout. To get your OpenACS code into your local CVS
+        1(b) should be labelled Step 1.
Figure 5.2. Upgrading a local CVS repository

Step 0: Set up a working CVS checkout. To get your OpenACS code into your local CVS
                 repository, you will set up a working CVS checkout of
                 OpenACS. When you want to update your site, you'll
                 update the working CVS checkout, import those changes
@@ -97,7 +97,7 @@
       
[$OPENACS_SERVICE_NAME ~]$ cd /var/lib/aolserver/$OPENACS_SERVICE_NAME
 [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ cvs up -Pd
 (CVS feedback)
-[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$
Upgrading a Production Site Safely
If you are upgrading a production OpenACS site which is on a private CVS tree, this process lets you do the upgrade without risking extended downtime or an unusable site:
Declare a freeze on new cvs updates - ie, you cannot run cvs update
+[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$

Upgrading a Production Site Safely

If you are upgrading a production OpenACS site which is on a private CVS tree, this process lets you do the upgrade without risking extended downtime or an unusable site:

Declare a freeze on new cvs updates - ie, you cannot run cvs update on the production site
Make a manual backup of the production site in addition to the automated backups
Import the new code (for example, OpenACS 5.0.4, openacs-5-0-compat versions of