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.18.2.3 -r1.18.2.4 --- openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html 30 Nov 2005 05:21:57 -0000 1.18.2.3 +++ openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html 1 Dec 2005 17:45:51 -0000 1.18.2.4 @@ -1,4 +1,4 @@ -Upgrading the OpenACS files

Upgrading the OpenACS files

Chosing a Method to Upgrade your Files

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

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 @@ -10,7 +10,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
    @@ -31,7 +31,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

    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

      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 @@ -95,7 +95,7 @@

        1. [$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:

      1. 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:

  1. Declare a freeze on new cvs updates - ie, you cannot run cvs update on the production site

  2. Make a manual backup of the production site in addition to the automated backups

  3. Import the new code (for example, OpenACS 5.0.4, openacs-5-0-compat versions of