Changeset 507 for branches/stable/INSTALL

Timestamp:

11/15/11 18:08:14 (12 years ago)

Author:

Kris Deugau

Message:

/branches/stable

Make the fixed web path at least configurable in one place rather
than completely hardcoded across many files.
Update initial database tabledef SQL
Bump version

File:

• branches/stable/INSTALL (modified) (3 diffs)

branches/stable/INSTALL

@@ -61 +61 @@
   b) Edit CustIDCK.pm as needed to validate customer IDs.
 
-4) Create the database, and the inital tables using cgi-bin/ipdb.psql.
+4) As a Postgres superuser, create a database user and the database.
+Create the inital tables using cgi-bin/ipdb.psql.
 
 5) Configure your webserver to call the IPDB scripts at an appropriate 
 web path.  A webroot pointing to the HTML files (first level under 
-the ipdb-#VERSION#/ tarball directory, or /usr/local/lib/ipdb-#VERSION#) 
-with a symlink or alias for ip/ -> . should work fine;  a server alias 
-under an existing virtual host should work as well.
+the ipdb-#VERSION#/ tarball directory, or /usr/local/lib/ipdb-#VERSION#)
+should work fine;  a server alias under an existing virtual host should
+work as well.
 
-Note that all URLs referenced internally currently assume they will be 
-presented at http://host/ip/;  you cannot put the IPDB at 
-http://host/noc/misc/ipdb/.
+Set $IPDB::webpath (the web path to your IPDB install) in MyIPDB.pm.
+Straight out of the tarball it should work at the webroot, but if you
+want it in a subdirectory, you'll need to set this variable to get all
+of the internal links to behave properly.
 
 The directory containing the HTML and scripts must have at least the 
 following Apache directives (or other server equivalent) set:
 
-  Options ExecCGI IncludesNoEXEC FollowSymlinks
+  Options ExecCGI IncludesNoEXEC
 
 6) User lists can be maintained two basic ways:
@@ -86 +88 @@
     remove the default user (or at least change its password).
 
-  b) Maintain an external .htpasswd file of your own, configured and 
+  b) Use the built-in user manager as in a) but create a short script to
+    export the user list to a standard .htpasswd file.  This may be
+    useful if mod_auth_pgsql isn't easily available.
+
+  c) Maintain an external .htpasswd file of your own, configured and 
     maintained however you like.  In this case the access-pwd-update.pl 
     script should edited to match the .htpasswd filename/path and should 
@@ -94 +100 @@
     in the database.
 
-You will have to either temporarily create a user "admin", so that user
-can grant other users priviledges, or run the following on the database:
+    You will have to either temporarily create a user "admin", so that user
+    can grant other users priviledges, or run the following on the database:
 
-  UPDATE users SET acl='bacdsA' WHERE username='newadminuser';
+      UPDATE users SET acl='bacdsA' WHERE username='newadminuser';
 
-Replace 'newadminuser' as appropriate.
+    Replace 'newadminuser' as appropriate.
 
-If you don't do this, nobody will be able to make any changes;  
-access-pwd-update.pl only grants minimal read access to new users.
+    If you don't do this, nobody will be able to make any changes;  
+    access-pwd-update.pl only grants minimal read access to new users.
 
 7) (optional) Pick a log facility by setting $IPDB::syslog_facility in