Index: openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.adp,v diff -u -r1.5.2.5 -r1.5.2.6 --- openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.adp 5 Jan 2021 17:33:40 -0000 1.5.2.5 +++ openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.adp 3 Sep 2021 09:15:37 -0000 1.5.2.6 @@ -1,5 +1,5 @@ -{/doc/acs-core-docs {ACS Core Documentation}} {Upgrading the OpenACS files} +{/doc/acs-core-docs/ {ACS Core Documentation}} {Upgrading the OpenACS files} Upgrading the OpenACS files Upgrading the OpenACS files

-Choosing a Method to Upgrade your +Choosing 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 filesystem (via any of the previous methods), and then using the APM to scan the filesystem, find upgrade scripts, and execute them. Starting with OpenACS 5.0, -the last method was added, which automatically changes the filesystem for you. If you are using the last method, you can skip this -page. This page 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” +the last method was added, which automatically changes the +filesystem for you. If you are using the last method, you can skip +this page. This page 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

    +Methods of upgrading OpenACS files

  • Upgrading files for a site which is not in a CVS @@ -53,7 +53,7 @@ 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 +

    Figure 5.2. Upgrading a local CVS repository

    Upgrading a local CVS repository

    • @@ -123,8 +123,7 @@ you have a local copy of the new OpenACS code, you need to import it into your local CVS repository and resolve any conflicts that occur.

      Import the new files into your cvs repository; where they match -existing files, they will become the new version of the file.

      -[$OPENACS_SERVICE_NAME openacs-5-1]$  cd /var/lib/aolserver/openacs-5-1
+existing files, they will become the new version of the file.
      [$OPENACS_SERVICE_NAME openacs-5-1]$  cd /var/lib/aolserver/openacs-5-1
 
 [$OPENACS_SERVICE_NAME openacs-5-1]$  cvs -d /var/lib/cvs import -m "upgrade to OpenACS 5.1" $OPENACS_SERVICE_NAME OpenACS openacs-5-1
 
@@ -143,8 +142,7 @@
 uses the cvs keyword yesterday, making the assumption that you
 haven't checked in new code to your local tree in the last day.
 This section should be improved to use tags instead of the keyword
-yesterday!
      -[$OPENACS_SERVICE_NAME openacs-5.1]$  cd /var/lib/aolserver
+yesterday!
      [$OPENACS_SERVICE_NAME openacs-5.1]$  cd /var/lib/aolserver
 [$OPENACS_SERVICE_NAME tmp]$ rm -rf $OPENACS_SERVICE_NAME-upgrade
 [$OPENACS_SERVICE_NAME tmp]$ mkdir $OPENACS_SERVICE_NAME-upgrade
 [$OPENACS_SERVICE_NAME tmp]$ cvs checkout -d $OPENACS_SERVICE_NAME-upgrade -jOpenACS:yesterday -jOpenACS -kk $OPENACS_SERVICE_NAME > cvs.txt 2>&1
@@ -182,7 +180,7 @@
 [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$

-Upgrading a Production Site Safely

If you are upgrading a production OpenACS site which is on a +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