Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/maintenance.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/maintenance.xml,v
diff -u -r1.35 -r1.36
--- openacs-4/packages/acs-core-docs/www/xml/install-guide/maintenance.xml 3 Nov 2018 19:57:22 -0000 1.35
+++ openacs-4/packages/acs-core-docs/www/xml/install-guide/maintenance.xml 3 Sep 2024 15:37:32 -0000 1.36
@@ -231,7 +231,7 @@
This script needs to be SUID-root, which means
that the script will run as root. This is necessary to ensure
that the AOLserver processes are killed regardless of who owns
- them. However the script should be executable by the
+ them. However, the script should be executable by the
web group to ensure that the
users updating the web page can use the script, but that
general system users cannot run the script. You also need to
@@ -339,7 +339,7 @@
to different values.
- Services on different host names
+ Services on different hostnamesFor example, suppose you want to support
http://service0.com and
http://bar.com on the same
@@ -351,8 +351,7 @@
- If you want to install two services with different host
- names sharing the same ip, you'll need nsvhr to redirect requests
+ If you want to install two services with different hostnames sharing the same ip, you'll need nsvhr to redirect requests
based on the contents of the tcp headers. See AOLserver
Virtual Hosting with TCP by markd.
@@ -492,7 +491,7 @@
Method 2: A/B DeploymentThe 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.
+ 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.Simple A/B Deployment: Database is not changed