SF.net SVN: ledger-smb:[3456] trunk/INSTALL

[..hidden..]

Revision: 3456
          http://ledger-smb.svn.sourceforge.net/ledger-smb/?rev=3456&view=rev
Author:   ehuelsmann
Date:     2011-07-06 21:51:13 +0000 (Wed, 06 Jul 2011)

Log Message:
-----------
Update bits of INSTALL, marking bits to be documented still.

Modified Paths:
--------------
    trunk/INSTALL

Modified: trunk/INSTALL
===================================================================
--- trunk/INSTALL	2011-07-06 14:45:03 UTC (rev 3455)
+++ trunk/INSTALL	2011-07-06 21:51:13 UTC (rev 3456)
@@ -4,14 +4,20 @@
 --------
 
  * System requirements
+ * Installing Apache 2
+ * Installing PostgreSQL
+ * PostgreSQL authorization settings
  * Installing Perl module dependencies
    * for Debian
    * for Fedora
    * for <your system>
+ * Initializing a company database
  * Adding configuration to Apache 2.x
- * Initializing a company database
+ * Manual configuration
+ * Company database removal
 
 
+
 System requirements
 ===================
 
@@ -54,6 +60,20 @@
 instructions for your system for inclusion here.
 
 
+PostgreSQL authorization settings (pg_hba.conf)
+===============================================
+
+pg_hba.conf settings for production
+-----------------------------------
+
+<section to be filled out>
+
+pg_hba.conf settings during setup (tools/prepare-company-database.sh)
+---------------------------------------------------------------------
+
+<section to be filled out>
+
+
 Installing Perl module dependencies
 ===================================
 
@@ -209,9 +229,13 @@
 up databases to be used for LedgerSMB. The script should be run as 'root'
 because it wants to 'su' to the postgres user.  Alternatively, if you
 know the password of the postgres user, you can run the script as any other
-user.  You'll be prompted for the password.
+user.  You'll be prompted for the password.  Additionally, the script creates
+a superuser to assign ownership of the created company database to. By
+default this user is called 'ledgersmb'.  The reason for this choice is that
+when removing the ledgersmb user, you'll be told about any unremoved parts
+of the database, because the owner of an existing database can't be removed
+until that database is itself removed.
 
-
 The following invocation of the script sets up your first test company,
 when invoked as the root user and from the root directory of the LedgerSMB
 sources:
@@ -232,7 +256,17 @@
 All these can be adjusted using arguments provided to the setup script. See
 the output generated by the --help option for a full list of options.
 
+Note: The script expects to be able to connect to the postgresql database
+      server over a TCP/IP connection after initial creation of the ledgersmb
+      user.  The ledgersmb user will be used to log in. To ensure that's
+      possible, it's easiest to ensure there's a row in the pg_hba.conf file
+      [the file which says how PostgreSQL should enforce its login policy]
+      with a 'host' configuration for the 127.0.0.1/32 address and the md5
+      authentication enforcement.  This line can be inserted for the duration
+      of the configuration of LedgerSMB, if the file doesn't have one.  The
+      line can safely be removed afterwards.
 
+
 Adding configuration to Apache 2.x
 ==================================
 


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.