From 2bc2d7d26c4c25dfa390defd4df645ac82d90c2d Mon Sep 17 00:00:00 2001 From: einhverfr Date: Tue, 6 Mar 2007 06:26:49 +0000 Subject: reworking INSTALL instructions so that Build test doesn;t generate spurious errors git-svn-id: https://ledger-smb.svn.sourceforge.net/svnroot/ledger-smb/branches/1.2@855 4979c152-3d1c-0410-bac9-87ea11338e46 --- INSTALL | 46 +++++++++++++++++++++++----------------------- 1 file changed, 23 insertions(+), 23 deletions(-) diff --git a/INSTALL b/INSTALL index b36183a0..f62fbb68 100644 --- a/INSTALL +++ b/INSTALL @@ -14,32 +14,13 @@ MANUAL INSTALL: 1) Untar in desired location. -2) 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 -missing. To check for dependencies, run "perl Build.PL" from the command line. -Missing dependencies can generally be installed via a Linux distributor's -package manager or by CPAN. (Build.PL itself uses Module::Build, which is -available in packages like perl-Module-Build or libmodule-build-perl.) - -Once this is done and dependencies are satisfied, you can check to see whether -the installation nominally works by running "./Build test" from the command -line. The test suites currently check to make sure all the perl modules load -and that a number of numeric tests are passed. - -Dependencies which are recommended are needed only for specific functionality -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 - -3) Decide where to put the user/session management tables. In general, we +2) Decide where to put the user/session management tables. In general, we 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. -4) Create central database +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. @@ -48,12 +29,31 @@ recommend as follows: Note that the psql connection should use the same username that you intend to use for the user authentication connection. -5) Set the admin password: +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. -6) Edit the ledger-smb.conf file as appropriate. +5) Edit the ledger-smb.conf file as appropriate. Congratulations, you have manually installed LedgerSMB 1.2. +6) 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 +missing. To check for dependencies, run "perl Build.PL" from the command line. +Missing dependencies can generally be installed via a Linux distributor's +package manager or by CPAN. (Build.PL itself uses Module::Build, which is +available in packages like perl-Module-Build or libmodule-build-perl.) + +Once this is done and dependencies are satisfied, you can check to see whether +the installation nominally works by running "./Build test" from the command +line. The test suites currently check to make sure all the perl modules load +and that a number of numeric tests are passed. + +Dependencies which are recommended are needed only for specific functionality +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 + -- cgit v1.2.3