Index: openacs-4/packages/acs-core-docs/www/openacs.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/openacs.html,v diff -u -r1.22.2.6 -r1.22.2.7 --- openacs-4/packages/acs-core-docs/www/openacs.html 18 Dec 2003 10:04:26 -0000 1.22.2.6 +++ openacs-4/packages/acs-core-docs/www/openacs.html 11 Jan 2004 12:45:46 -0000 1.22.2.7 @@ -1,7 +1,7 @@ -
by Vinod Kurup
+by Vinod Kurup
For Linux Standard Base compliance and ease of backup, +
For Linux Standard Base compliance and ease of backup,
all of the files in each OpenACS site are stored in a
subdirectory of
/var/lib/aolserver, one
@@ -10,9 +10,9 @@
[root root]# chgrp web /var/lib/aolserver
[root root]# chmod 770 /var/lib/aolserver
[root root]#
-mkdir /var/lib/aolserver
+mkdir /var/lib/aolserver
chgrp web /var/lib/aolserver
-chmod 770 /var/lib/aolserver
AOLserver needs to be started as the root user if you want to use port 80. Once it starts, though, it will drop the root privileges and run as another user, which you must specify on the command line. It's @@ -34,6 +34,7 @@ it in the service0 group so that it can use database and server commands associated with that group.
[root root]# groupadd web +[root root]# groupadd service0 [root root]# useradd -g service0 -G web service0 -d /home/service0 [root root]#
Starting with OpenACS 5.0, an experimental script is available to automate all of the steps for the rest of this @@ -71,8 +72,8 @@ tarball and save it in /tmp and proceed:
Unpack the OpenACS tarball and rename it to service0. Secure the directory so that only the owner can access it. Check the permissions by listing the directory.
[root root]# su - service0
[service0 service0]$ cd /var/lib/aolserver
-[service0 aolserver]$ tar xzf /tmp/openacs-5.0.0b4.tgz
-[service0 aolserver]$ mv openacs-5.0.0b4 service0
+[service0 aolserver]$ tar xzf /tmp/openacs-5.0.0rc1.tgz
+[service0 aolserver]$ mv openacs-5.0.0rc1 service0
[service0 aolserver]$ chmod -R 700 service0
[service0 aolserver]$ ls -al
total 3
@@ -82,12 +83,12 @@
[service0 aolserver]$ exit
logout
[root root]#
-su - service0
+su - service0
cd /var/lib/aolserver
-tar xzf /tmp/openacs-5.0.0b4.tgz
-mv openacs-5.0.0b4 service0
+tar xzf /tmp/openacs-5.0.0rc1.tgz
+mv openacs-5.0.0rc1 service0
chmod -R 700 service0/
-exit
Add the Service to CVS (OPTIONAL)
Prepare the database
Prepare Oracle for OpenACS.�If you won't be using Oracle, skip to Prepare PostgreSQL for an OpenACS Service
+exit
Add the Service to CVS (OPTIONAL)
Prepare the database
Prepare Oracle for OpenACS.�If you won't be using Oracle, skip to Prepare PostgreSQL for an OpenACS Service
You should be sure that your user account (e.g. service0) is in the dba group. @@ -219,16 +220,16 @@ [service0 service0]$ createdb -E UNICODE service0 CREATE DATABASE [service0 service0]$ -su - service0 -createdb -E UNICODE service0
Automate daily database Vacuuming. This is a process which cleans out discarded data from the database. A quick way to automate vacuuming is to edit the cron file for the database user. Recommended: VACUUM ANALYZE every hour and VACUUM FULL ANALYZE every day.
[service0 service0]$ export EDITOR=emacs;crontab -e
Add this line to the file. The numbers and stars at the beginning are cron columns that specify when the program should be run - in this case, whenever the minute is 0 and the hour is 1, i.e., 1:00 am every day.
0 1-23 * * * /usr/local/pgsql/bin/vacuumdb --full --analyze service0
+su - service0
+createdb -E UNICODE service0
Automate daily database Vacuuming. This is a process which cleans out discarded data from the database. A quick way to automate vacuuming is to edit the cron file for the database user. Recommended: VACUUM ANALYZE every hour and VACUUM FULL ANALYZE every day.
[service0 service0]$ export EDITOR=emacs;crontab -e
Add this line to the file. The numbers and stars at the beginning are cron columns that specify when the program should be run - in this case, whenever the minute is 0 and the hour is 1, i.e., 1:00 am every day.
0 1-23 * * * /usr/local/pgsql/bin/vacuumdb --full --analyze service0 0 0 * * * /usr/local/pgsql/bin/vacuumdb --full --analyze service0
Add Full Text Search Support (OPTIONAL)
At this point the database should be ready for installing OpenACS.
Configure an AOLserver Service for OpenACS.�
The AOLserver architecture lets you run an arbitrary number of virtual servers. A virtual server is an HTTP service running on a specific port, e.g. port 80. In order for OpenACS to work, you need to configure a virtual server. The Reference Platform uses a configuration file included in the OpenACS tarball, /var/lib/aolserver/service0/etc/config.tcl. - Open it in an editor to adjust the parameters.
[root root]# su - service0 + Open it in an editor to adjust the parameters.[root root]# su - service0 [service0 service0]$ cd /var/lib/aolserver/service0/etc [service0 etc]$ emacs config.tcl@@ -293,7 +294,7 @@ AOLserver keepalive (OPTIONAL)
Configure a Service with the OpenACS Installer.� Now that you've got AOLserver up and running, let's install OpenACS - 5.0.0b4. + 5.0.0rc1.
You should see a page from the webserver titled OpenACS Installation: @@ -349,7 +350,7 @@ Give the server a few minutes to start up. Then reload the final page above. You should see the front page, with an area to login near the upper right. Congratulations, OpenACS - 5.0.0b4 is now up and running! + 5.0.0rc1 is now up and running!
Install Full Text Search (OPTIONAL). If you have installed OpenFTS and enabled OpenFTS, you can now install the OpenFTS Driver package and Full Text Search Engine package in the OpenACS service.
This is a good time to make a backup of your service. If this is a