Index: openacs-4/packages/acs-automated-testing/www/doc/usage.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-automated-testing/www/doc/usage.adp,v
diff -u -r1.4 -r1.5
--- openacs-4/packages/acs-automated-testing/www/doc/usage.adp	30 Apr 2018 08:13:40 -0000	1.4
+++ openacs-4/packages/acs-automated-testing/www/doc/usage.adp	3 Sep 2024 15:37:30 -0000	1.5
@@ -1,7 +1,11 @@
 
-<property name="context">{/doc/acs-automated-testing {ACS Automated Testing}} {Usage}</property>
+<property name="context">{/doc/acs-automated-testing/ {ACS Automated Testing}} {Usage}</property>
 <property name="doc(title)">Usage</property>
 <master>
+<style>
+div.sect2 > div.itemizedlist > ul.itemizedlist > li.listitem {margin-top: 16px;}
+div.sect3 > div.itemizedlist > ul.itemizedlist > li.listitem {margin-top: 6px;}
+</style>              
 <include src="/packages/acs-core-docs/lib/navheader"
 			leftLink="install" leftLabel="Prev"
 			title=""
@@ -13,7 +17,11 @@
 Aufrecht</a>
 </p>
 OpenACS docs are written by the named authors, and may be edited by
-OpenACS documentation staff.</div><p>Here&#39;s the entire chain of code used to set up
+OpenACS documentation staff.</div><p>This documentation refers to the setup of the OpenACS
+test-servers of 2003. This setup was active probably around 5
+years, and is obsolete. Use regression testing of your local
+instance and Refer to a CI/CD pipeline as presented at the OpenACS
+conference in 2022.</p><p>Here&#39;s the entire chain of code used to set up
 auto-rebuilding servers on test.openacs.org</p><div class="itemizedlist"><ul type="disc">
 <li>
 <p>The master server shows the status of all other servers. For
@@ -26,14 +34,12 @@
 <li><p>Suppose the first test server is <span class="replaceable"><span class="replaceable">service1</span></span>. Set
 up a dedicated user and <a href="http://openacs.org/doc/openacs-5-0-0/openacs.html#install-with-script" target="_top">automated install script</a>.</p></li><li>
 <p>To run automated testing automatically each time the server is
-rebuilt, add this to /home/service1/install/install.tcl:</p><pre class="programlisting">
-set do_tclapi_testing "yes"</pre>
+rebuilt, add this to /home/service1/install/install.tcl:</p><pre class="programlisting">       set do_tclapi_testing "yes"</pre>
 </li><li>
 <p>Get the results of the automated tests dumped where the master
 server can see them - in this example, the same directory as above,
 <tt class="computeroutput">/var/log/openacs-install</tt>, by adding
-this to install.tcl (requires 5.1):</p><pre class="programlisting">
-set install_xml_file          "/var/lib/aolserver/service0/packages/acs-core-docs/www/files/install-autotest.xml"</pre><p>This will copy in the file <tt class="computeroutput">install-autotest.xml</tt>:</p><pre class="programlisting">&lt;?xml version="1.0"?&gt;
+this to install.tcl (requires 5.1):</p><pre class="programlisting">          set install_xml_file          "/var/lib/aolserver/service0/packages/acs-core-docs/www/files/install-autotest.xml"</pre><p>This will copy in the file <tt class="computeroutput">install-autotest.xml</tt>:</p><pre class="programlisting">&lt;?xml version="1.0"?&gt;
 
 &lt;!-- This is an install.xml which can be used to configure servers for reporting their automated test results.  Requires acs-automated-testing 5.1.0b2 or better --&gt;
 
@@ -65,8 +71,7 @@
 
 sudo /home/$1/install/install.sh 2&gt;&amp;1</pre><p>and allow the <tt class="computeroutput">master</tt> user to
 execute this file as root (this is a limitation of the automatic
-install script, which must be root). In <tt class="computeroutput">/etc/sudoers</tt>, include a line:</p><pre class="programlisting">
-master ALL = NOPASSWD: /usr/local/bin/rebuild-server.sh</pre>
+install script, which must be root). In <tt class="computeroutput">/etc/sudoers</tt>, include a line:</p><pre class="programlisting">master ALL = NOPASSWD: /usr/local/bin/rebuild-server.sh</pre>
 </li>
 </ul></div>
 </div>