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 @@ -102,7 +102,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 @@ -113,32 +113,33 @@ 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 filesystem 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.
This approach can has limitations. If the database or filesystem +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.