From 1d323f4d638f01dbf20a0f8151322ea611a8dd1b Mon Sep 17 00:00:00 2001
From: einhverfr <einhverfr@4979c152-3d1c-0410-bac9-87ea11338e46>
Date: Sat, 17 Mar 2007 22:12:29 +0000
Subject: Updated INSTALL based on Jeffk's suggestions

git-svn-id: https://ledger-smb.svn.sourceforge.net/svnroot/ledger-smb/branches/1.2@936 4979c152-3d1c-0410-bac9-87ea11338e46
---
 INSTALL | 61 ++++++++++++++++++++++++++++++++++++++++++++-----------------
 1 file changed, 44 insertions(+), 17 deletions(-)

(limited to 'INSTALL')

diff --git a/INSTALL b/INSTALL
index bd2cd34e..1f4dca68 100644
--- a/INSTALL
+++ b/INSTALL
@@ -24,32 +24,50 @@ recommend as follows:
   a)  Single dataset installations should use the user tables in the dataset.
   b)  Multicompany installations should use user tables in a separate dataset
       from any accounting data.
+To be integrated into the documentation, these minimalist steps have made
+installation/migration of ledger-smb much easier for me:
 
-3)  Create central database
 
-  a) cd to the sql/ directory of the new ledger directory.
-  b) run "psql" with appropriate options to connect to your database.
-  c) Run the SQL script Pg-central.sql.
-        From psql, the command is:  \i /path/to/Pg-Central.sql
-  d) If you are going to put your data here too, run the following command:
-	CREATE LANGUAGE PLPGSQL;
+3) Create a admin database role named 'ledgersmb':
 
-  Note that the psql connection should use the same username that you intend to
-  use for the user authentication connection.  If you use a different username
-  you may find that you get an Access Denied message.
+    bash$ createuser --no-superuser --createdb --no-createrole -U postgres
+     --pwprompt --encrypted ledgersmb
 
-4)  Set the admin password:
-  a)  From psql, determine what admin password you wish to use.  Then type:
-      "update users_conf set password = md5('my_password');"
-      Naturally you would use your password instead of my_password.
 
+4) Create a central user database database, owned by admin role:
 
-5)  Edit the ledger-smb.conf file as appropriate.
+    bash$ createdb -U ledgersmb -O ledgersmb ledgersmb
+
+
+5) Run the included SQL commands to configure the central user database:
+
+    bash$ psql -U ledgersmb -d ledgersmb -f (ledgerpath)/sql/Pg-central.sql
+
+
+6) Update your admin password in the central user database
+    (change MYPASSWORD to your preferred administrative password).
+
+    bash$ psql -U ledgersmb -d ledgersmb
+
+    ledgersmb=> UPDATE users_conf SET password = md5('MYPASSWORD') WHERE id = 1;
+
+7) Quit the interactive SQL console:
+
+    ledgersmb=> \q
+
+Configure apache, visit admin.pl, login with MYPASSWORD, create datasets
+with user ledgersmb, superuser postgres, create users pointing to datasets,
+etc.
+
+
+8)  Edit the ledger-smb.conf file as appropriate.
   a)  Make sure to set the section under GlobalDBH to point to hte databae you
       imported Pg-central into.
-Congratulations, you have manually installed LedgerSMB 1.2.
 
-6)  Check Dependencies
+9)  Add configuration to Apache:
+    bash$ sh configure_apache.sh
+
+10) Check Dependencies
 
 The Build.PL script can be used to test for unmet dependencies and run other
 tests.  It doesn't install anything yet, but it will tell you what you are 
@@ -68,6 +86,15 @@ and may not be required in all circumstances.  These include:
   * Net::TCLink for credit card processing in a POS environment
   * Parse::RecDescent for the CLI script host
 
+11) Restart Apache (instructions may vary with your Linux distro).
+
+12) Create Datasets and Users:
+   Visit http://hostname/ledger-smb/admin.pl, login with MYPASSWORD, 
+   Create datasets with user ledgersmb, superuser postgres
+   Create users pointing to datasets.
+
+Congratulations, you have manually installed LedgerSMB 1.2.
+
 
 FTP INSTALLATION:
 ============================================================================
-- 
cgit v1.2.3