Index: openacs-4/packages/acs-core-docs/www/install-overview.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-overview.html,v diff -u -r1.7.2.8 -r1.7.2.9 --- openacs-4/packages/acs-core-docs/www/install-overview.html 4 May 2003 06:30:02 -0000 1.7.2.8 +++ openacs-4/packages/acs-core-docs/www/install-overview.html 7 May 2003 17:40:58 -0000 1.7.2.9 @@ -1,17 +1,17 @@ -
The basic steps to getting OpenACS up and running are:
Install an OS
Install a webserver (AOLServer)
Install a database (Oracle or PostgreSQL)
Install a database driver (allows the webserver to talk to the database) -
Start the OpenACS installer, which will configure a database instance..
This is text you will see on - screen, such as a link - in a radio button list or menu.
orThis is text that you will type.
This is text from a program or file which you may need to +
Start the OpenACS installer, which will configure a database instance..
This is text you will see on + screen, such as a link + in a radio button list or menu.
orThis is text that you will type.
This is text from a program or file which you may need to examine or edit:
if {$database == "oracle"} { set db_password "mysitepassword" }
This is text that you will -see and type in a command shell, including text you may have to -change. It is followed by a list of just the commands, -which you can copy and paste.
[root@localhost root]# su - nsadmin -[nsadmin@localhost aolserver]$ svc -d /service/server1 -[nsadmin@localhost aolserver]$ dropdb server1 +see and type in a command shell, including text you may have to +change. It is followed by a list of just the commands, +which you can copy and paste.[root@localhost root]# su - nsadmin +[nsadmin@localhost aolserver]$ svc -d /service/server1 +[nsadmin@localhost aolserver]$ dropdb server1 DROP DATABASE -[nsadmin@localhost aolserver]$ createdb server1 +[nsadmin@localhost aolserver]$ createdb server1 CREATE DATABASE -su - nsadmin -svc -d /service/server1 -dropdb server1 -createdb server1
We'll do our best to assure that following our instructions will get you to the promised land. If something goes wrong, don't panic. There are plenty of ways to get help. Here are some tips:
Keep track of the commands you are run and record their output. I like to do my installations in a shell inside of emacs - (M-x shell) so that I can save + (M-x shell) so that I can save the output if needed. An alternative would be to use the - script command. + script command.
We'll point out where the error logs for the various pieces of software are. Output from those logs will help us help you. Don't @@ -131,7 +131,7 @@ If you find errors in this document or if you have ideas about making it better, please post them in our BugTracker. -
After reading through this tome, you may ask yourself if there is a better way. Well, not quite. Jonathan Marsden has created RPMs (at @@ -140,7 +140,7 @@ 4.6.3. There has been talk about automating the install process, but that hasn't happened yet. Stay tuned! -
This document was created by Vinod Kurup, but it's really just plagiarism from a number of documents that came before it. If I've used something that you've written without proper credit, let me @@ -161,7 +161,7 @@ Aufrecht's OpenACS 4.5 Quick Guide.
Please also see the Credits section for more acknowledgements. -
Here's a list of some helpful documentation for various OS's
Once you get your OS installed, it's imperative that you secure your installation. As Jon Griffin repeatedly warns us, "No distribution is secure out of the box." The Reference Platform implements @@ -207,9 +207,9 @@
Bruce Schneier's Crypto-Gram, especially The - security patch treadmill and Monitoring First.
+ security patch treadmill and Monitoring First.
Here are some resources that OpenACS users have found useful. -
+
Philip and Alex's Guide to Web Publishing - A very readable @@ -242,7 +242,7 @@ Linux in a Nutshell -