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.17 -r1.1.2.18 --- openacs-4/packages/acs-core-docs/www/maintenance-deploy.adp 11 Jun 2017 08:42:13 -0000 1.1.2.17 +++ openacs-4/packages/acs-core-docs/www/maintenance-deploy.adp 15 Jun 2017 13:56:42 -0000 1.1.2.18 @@ -11,8 +11,8 @@
This section describes two minimal-risk methods for deploying @@ -24,7 +24,7 @@ working configuration safely and quickly.
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 ...
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.