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.1.2.12 -r1.1.2.13 --- openacs-4/packages/acs-core-docs/www/maintenance-deploy.adp 23 Jun 2016 08:32:45 -0000 1.1.2.12 +++ openacs-4/packages/acs-core-docs/www/maintenance-deploy.adp 19 Nov 2016 09:21:54 -0000 1.1.2.13 @@ -1,5 +1,5 @@ -{/doc/acs-core-docs {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-deploy.html,v 1.24.2.10 -2016/06/21 07:44:36 gustafn Exp $)

By Joel Aufrecht +

($‌Id: maintenance.xml,v 1.30.6.1 2016/06/23 +08:32:46 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 @@ -103,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 @@ -119,28 +119,28 @@ function or 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 +

Figure 6.2. Simple A/B Deployment - Step 1

Simple A/B Deployment - Step 1

-

Figure 6.3. Simple +

Figure 6.3. Simple A/B Deployment - Step 2

Simple A/B Deployment - Step 2

-

Figure 6.4. Simple +

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 +

Figure 6.5. Complex A/B Deployment - Step 1

Complex A/B Deployment - Step 1

-

Figure 6.6. Complex A/B Deployment +

Figure 6.6. Complex A/B Deployment - Step 2

Complex A/B Deployment - Step 2

-

Figure 6.7. Complex A/B Deployment +

Figure 6.7. Complex A/B Deployment - Step 3

Complex A/B Deployment - Step 3