| OpenACS service |
+createdb $OPENACS_SERVICE_NAME Setting a global shell variable for cut and paste. In order to cut and paste the instructions into your shell, you must set the environment variable $OPENACS_SERVICE_NAME. In order to set it globally so that it works for any new users or special service users you may create, edit the file /etc/profile ( /etc/share/skel/dot.profile for FreeBSD) and add this line: export OPENACS_SERVICE_NAME=service0 Table 2.1. Default directories for a standard install | Fully qualified domain name of your server | yourserver.test | | name of administrative access account | remadmin | | OpenACS service |
$OPENACS_SERVICE_NAME (set to service0 in default install) | | OpenACS service account | $OPENACS_SERVICE_NAME | | OpenACS database name | $OPENACS_SERVICE_NAME | | Root of OpenACS service file tree (SERVERROOT) | /var/lib/aolserver/$OPENACS_SERVICE_NAME | | Location of source code tarballs for new software | /var/tmp | | The OpenACS tarball contains some files which
are useful while setting up other software. Those
files are located at: | /var/tmp/openacs-5.9.0/packages/acs-core-docs/www/files | | Database backup directory | /var/lib/aolserver/$OPENACS_SERVICE_NAME/database-backup | | Service config files | /var/lib/aolserver/$OPENACS_SERVICE_NAME/etc | | Service log files | /var/lib/aolserver/$OPENACS_SERVICE_NAME/log | | Compile directory | /usr/local/src | | PostgreSQL directory | /usr/local/pgsql | | AOLserver directory | /usr/local/aolserver |
- 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. Getting Help during installation
- 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
|