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.30 -r1.31 --- openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html 24 Mar 2018 00:14:57 -0000 1.30 +++ openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html 25 Apr 2018 08:38:28 -0000 1.31 @@ -2,7 +2,7 @@ Upgrading the OpenACS files

Upgrading the OpenACS files

-

Choosing a Method to Upgrade your Files

+

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

-

Methods of upgrading OpenACS files

+

Methods of upgrading OpenACS files

  • @@ -57,7 +57,7 @@ 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

    +

    Figure 5.2. Upgrading a local CVS repository

    Upgrading a local CVS repository

    @@ -192,7 +192,7 @@ [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$
-

Upgrading a Production Site Safely

+

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: