Index: openacs-4/packages/acs-core-docs/www/maintenance-deploy.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/maintenance-deploy.html,v diff -u -r1.27 -r1.28 --- openacs-4/packages/acs-core-docs/www/maintenance-deploy.html 27 Mar 2018 11:18:00 -0000 1.27 +++ openacs-4/packages/acs-core-docs/www/maintenance-deploy.html 25 Apr 2018 08:38:28 -0000 1.28 @@ -12,7 +12,7 @@

Rollback: If anything goes wrong, you can return to the previous working configuration safely and quickly.

-

Method 1: Deployment with CVS

+

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 @@ -111,36 +111,36 @@

-

Method 2: A/B Deployment

+

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 you can see them directly. It does not, by itself, guarantee the entire control chain. You need additional measures to make sure that the change you are making is exactly and completely the change you intended to make and tested previously, and nothing more. Those additional measures typically take the form of source control tags and system version numbers. The parallel-server approach also guarantees rollback because the original working service is not touched; it is merely set aside.

This approach can has limitations. If the database or file system regularly receiving new data, you must interrupt this 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 changed

+

Simple A/B Deployment: Database is not changed

-

Figure 6.2. 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

+

Figure 6.3. Simple A/B Deployment - Step 2

Simple A/B Deployment - Step 2

-

Figure 6.4. 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 changed

+

Complex A/B Deployment: Database is changed

-

Figure 6.5. 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

+

Figure 6.6. Complex A/B Deployment - Step 2

Complex A/B Deployment - Step 2

-

Figure 6.7. Complex A/B Deployment - Step 3

+

Figure 6.7. Complex A/B Deployment - Step 3

Complex A/B Deployment - Step 3