Index: openacs-4/packages/acs-core-docs/www/maintenance-deploy.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/maintenance-deploy.adp,v diff -u -r1.5.2.9 -r1.5.2.10 --- openacs-4/packages/acs-core-docs/www/maintenance-deploy.adp 27 Apr 2022 16:52:20 -0000 1.5.2.9 +++ openacs-4/packages/acs-core-docs/www/maintenance-deploy.adp 13 Jul 2023 12:43:21 -0000 1.5.2.10 @@ -1,18 +1,18 @@ -{/doc/acs-core-docs {ACS Core Documentation}} {Staged Deployment for Production Networks} +{/doc/acs-core-docs/ {ACS Core Documentation}} {Staged Deployment for Production Networks} Staged Deployment for Production Networks

Staged Deployment for Production Networks

-
($‌Id: maintenance.xml,v 1.35.2.2 2020/07/02 -08:39:25 gustafn Exp $)

By Joel Aufrecht +

($‌Id: maintenance.xml,v 1.35.2.4 2023/07/10 +08:36:09 gustafn Exp $)

By Joel Aufrecht

OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff.

This section describes two minimal-risk methods for deploying @@ -24,7 +24,7 @@ working configuration safely and quickly.

-Method 1: Deployment with CVS

With this method, we control the files on a site via CVS. This +Method 1: Deployment with CVS

With this method, we control the files on a site via CVS. This example uses one developmental server (service0-dev) and one production server (service0). Depending on your needs, you can also have a staging server for extensive testing before you go live. The @@ -86,7 +86,8 @@

To make these changes take place on service0:

 4) update the file on production:
 cd /var/lib/aolserver/service0/www
-cvs up -Pd index.adp

If you make changes that require changes to the database, test +cvs up -Pd index.adp +

If you make changes that require changes to the database, test them out first on service0-dev, using either -create.sql or upgrade scripts. Once you've tested them, you then update and run the upgrade scripts from the package manager.

The production site can run "HEAD" from cvs.

The drawback to using HEAD as the live code is that you cannot @@ -102,7 +103,7 @@ tags to follow ...

-Method 2: A/B Deployment

The approach taken in this section is to always create a new +Method 2: A/B Deployment

The approach taken in this section is to always create a new service with the desired changes, running in parallel with the existing site. This guarantees control, at least at the final step of the process: you know what changes you are about to make because @@ -118,29 +119,29 @@ risk losing data in the shuffle. It also requires extra steps if the database will be affected.

-Simple A/B Deployment: Database is not +Simple A/B Deployment: Database is not changed

-

Figure 6.2. Simple A/B -Deployment - Step 1

Simple A/B Deployment - Step 1
+

Figure 6.2. Simple +A/B Deployment - Step 1

Simple A/B Deployment - Step 1

-

Figure 6.3. Simple A/B -Deployment - Step 2

Simple A/B Deployment - Step 2
+

Figure 6.3. Simple +A/B Deployment - Step 2

Simple A/B Deployment - Step 2

-

Figure 6.4. Simple A/B -Deployment - Step 3

Simple A/B Deployment - Step 3
+

Figure 6.4. Simple +A/B Deployment - Step 3

Simple A/B Deployment - Step 3

-Complex A/B Deployment: Database is +Complex A/B Deployment: Database is changed

-

Figure 6.5. Complex A/B -Deployment - Step 1

Complex A/B Deployment - Step 1
+

Figure 6.5. Complex A/B Deployment +- Step 1

Complex A/B Deployment - Step 1

-

Figure 6.6. Complex A/B -Deployment - Step 2

Complex A/B Deployment - Step 2
+

Figure 6.6. Complex A/B Deployment +- Step 2

Complex A/B Deployment - Step 2

-

Figure 6.7. Complex A/B -Deployment - Step 3

Complex A/B Deployment - Step 3
+

Figure 6.7. Complex A/B Deployment +- Step 3

Complex A/B Deployment - Step 3