Index: openacs-4/packages/acs-core-docs/www/install-steps.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-steps.html,v diff -u -r1.35.2.10 -r1.35.2.11 --- openacs-4/packages/acs-core-docs/www/install-steps.html 21 Jun 2016 07:44:36 -0000 1.35.2.10 +++ openacs-4/packages/acs-core-docs/www/install-steps.html 23 Jun 2016 08:32:45 -0000 1.35.2.11 @@ -48,8 +48,8 @@ $OPENACS_SERVICE_NAME (set to service0 in default install)
- None of these locations are set in stone - they're simply - the values that we've chosen. The values that you'll + None of these locations are set in stone - they're simply + the values that we've chosen. The values that you'll probably want to change, such as service name, are marked like this. The other values we recommend you leave unchanged unless you have a @@ -58,8 +58,8 @@ those recommended in previous versions of this document to improve security and maintainability. See this thread for discussion.
- We'll do our best to assure that following our instructions will get - you to the promised land. If something goes wrong, don't + 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
@@ -68,30 +68,30 @@
the output if needed. An alternative would be to use the
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 + 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 worry if you feel overwhelmed by all the information in the error - logs. Over time, you'll find that they make more and more - sense. Soon, you'll actually look forward to errors so that you + logs. Over time, you'll find that they make more and more + sense. Soon, you'll actually look forward to errors so that you can run to the log and diagnose the problem.
Search the forums at - openacs.org - you'll often find many people who have - struggled through the same spot that you're in. + openacs.org - you'll often find many people who have + struggled through the same spot that you're in.
The bottom of each page has a link to OpenACS.org, where you can post comments and read other users comments about the contents of the page.
Ask questions at the irc channel on freenode.net - (#openacs). They're knowledgeable and quite friendly + (#openacs). They're knowledgeable and quite friendly if you can keep them on topic.
Post a question on the forums. Make sure - you've done a search first. When you do post, be sure to include + you've done a search first. When you do post, be sure to include your setup information (OS, etc) as well as the exact commands that are failing with the accompanying error. If - there's a SQL error in the Tcl error or in the log, + there's a SQL error in the Tcl error or in the log, post that too.
If you find errors in this document or if you have ideas about