| Prev | Chapter 5. Upgrading | Next |
|---|
OpenACS is distributed in many different ways: +
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” -
Upgrading files for a site which is not in a CVS repository. Unpack the tarball into a new directory and copy its +
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.
Step 0: Set up a working CVS checkout. To get your OpenACS code into your local CVS + 1(b) should be labelled Step 1.
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 @@ -65,7 +65,7 @@
Update CVS. Update your local CVS working checkout (unless you just set it up).
[root root]#su - $OPENACS_SERVICE_NAME[$OPENACS_SERVICE_NAME aolserver]$cd /var/lib/aolserver/openacs-5-1-[$OPENACS_SERVICE_NAME aolserver]$cvs up -Pd ChangeLog *.txt bin etc tcl www packages/*Update a single package via cvs working checkout. You can add or upgrade a single package at a time, if you already have a cvs working directory.
[root root]#su - $OPENACS_SERVICE_NAME+[$OPENACS_SERVICE_NAME aolserver]$cvs up -Pd ChangeLog *.txt bin etc Tcl www packages/*Update a single package via cvs working checkout. You can add or upgrade a single package at a time, if you already have a cvs working directory.
[root root]#su - $OPENACS_SERVICE_NAME[$OPENACS_SERVICE_NAME aolserver]$cd /var/lib/aolserver/packages/openacs-5-1[$OPENACS_SERVICE_NAME openacs-5-1]$cvs up -Pd packagenameIn the next section, the import must be tailored to just this package.
Step 2: Merge New OpenACS code. Now that 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[$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@@ -97,7 +97,7 @@
cd /var/lib/aolserver/$OPENACS_SERVICE_NAME[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$cvs up -Pd(CVS feedback) -[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$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]$
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
