Running OpenACS in Production Environments

+Running OpenACS in Production Environments

Prev	Chapter�6.�Maintenance	Next

Running OpenACS in Production Environments

By Joel Aufrecht

OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff.

Maintenance tasks, optional software, and alternate configurations for AOLserver.

Starting and Stopping an OpenACS instance.

The simplest way to start and stop and OpenACS site is to run the startup shell script provided, /var/lib/aolserver/service0/etc/daemontools/run. This runs as a regular task, and logs to the logfile. To stop the site, kill the script.

A more stable way to run OpenACS is with a "keepalive" mechanism of some sort, so that whenever the server halts or is stopped for a reset, it restarts automatically. This is recommended for development and production servers.

The Reference Platform uses Daemontools to control AOLserver. A simpler method, using init, is here.

Daemontools must already be installed. If not, install it.
Each service controlled by daemontools must have a @@ -159,7 +159,7 @@ able to exploit your web server to execute a command on your server, they would not be able to gain root access.

Running multiple services on one machine

Services on different ports.�To run a different service on another port but the same - ip, simply repeat Install OpenACS replacing + ip, simply repeat Install OpenACS 5.0.1d1 replacing service0, and change the

set httpport              8000
 set httpsport             8443