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.14 -r1.1.2.15
--- openacs-4/packages/acs-core-docs/www/maintenance-deploy.adp 30 Nov 2016 08:15:11 -0000 1.1.2.14
+++ openacs-4/packages/acs-core-docs/www/maintenance-deploy.adp 6 Jan 2017 09:18:42 -0000 1.1.2.15
@@ -11,8 +11,8 @@
Staged Deployment for Production
Networks
-
($Id: maintenance-deploy.html,v 1.24.2.12
-2016/11/19 09:21:54 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
-Complex A/B Deployment: Database is
+Complex A/B Deployment: Database is
changed
