summaryrefslogtreecommitdiff
path: root/INSTALL
blob: 203e87dacd99507084fba6b81abdd7fa7ddb928a (plain)
  1. Installing LedgerSMB 1.2
  2. This document contains information on how to install LedgerSMB. We recommend
  3. that the reader start by reading the section on manual installation and then
  4. start by trying the automated means mentioned later.
  5. Also this document assumes that the reader is already familiar with the release
  6. notes. If you have not already done so, please read the release_notes file in
  7. the doc/ directory.
  8. DISTRO AND OS-SPECIFIC NOTES:
  9. ===============================================================================
  10. Debian users should read README.debian
  11. MANUAL INSTALL:
  12. ===============================================================================
  13. 1) Untar in desired location (for example, /usr/local/).
  14. 2) Decide where to put the user/session management tables. In general, we
  15. recommend as follows:
  16. a) Single dataset installations should use the user tables in the dataset.
  17. b) Multicompany installations should use user tables in a separate dataset
  18. from any accounting data.
  19. 3) Create a admin database role named 'ledgersmb':
  20. bash$ createuser --no-superuser --createdb --no-createrole -U postgres
  21. --pwprompt --encrypted ledgersmb
  22. 4) Create a central user database database, owned by admin role:
  23. bash$ createdb -U ledgersmb -O ledgersmb ledgersmb
  24. 5) Run the included SQL commands to configure the central user database:
  25. (ledgerpath) is wherever you untarred the file. If you untarred to
  26. /usr/local/ then it will be /usr/local/ledger-smb.
  27. bash$ psql -U ledgersmb -d ledgersmb -f (ledgerpath)/sql/Pg-central.sql
  28. 6) Update your admin password in the central user database
  29. (change MYPASSWORD to your preferred administrative password).
  30. bash$ psql -U ledgersmb -d ledgersmb
  31. ledgersmb=> UPDATE users_conf SET password = md5('MYPASSWORD') WHERE id = 1;
  32. 7) Quit the interactive SQL console:
  33. ledgersmb=> \q
  34. 7b) If you want to store the company information in the same database, run the
  35. following command:
  36. bash$ createlang -U postgres -d ledgersmb plpgsql;
  37. 8) Edit the ledger-smb.conf file as appropriate.
  38. b) Copy the ledger-smb.conf.default to ledger-smb.conf
  39. a) Make sure to set the section under [globaldbh] to point to thee database
  40. you imported Pg-central into.
  41. 9) Add configuration to Apache:
  42. bash$ sh configure_apache.sh
  43. 10) Check Dependencies
  44. The Build.PL script can be used to test for unmet dependencies and run other
  45. tests. It doesn't install anything yet, but it will tell you what you are
  46. missing. To check for dependencies, run "perl Build.PL" from the command line.
  47. Missing dependencies can generally be installed via a Linux distributor's
  48. package manager or by CPAN. (Build.PL itself uses Module::Build, which is
  49. available in packages like perl-Module-Build or libmodule-build-perl.)
  50. Once this is done and dependencies are satisfied, you can check to see whether
  51. the installation nominally works by running "./Build test" from the command
  52. line. The test suites currently check to make sure all the perl modules load
  53. and that a number of numeric tests are passed.
  54. Dependencies which are recommended are needed only for specific functionality
  55. and may not be required in all circumstances. These include:
  56. * Net::TCLink for credit card processing in a POS environment
  57. * Parse::RecDescent for the CLI script host
  58. 11) Restart Apache (instructions may vary with your Linux distro or operating
  59. system).
  60. 12) Create Datasets and Users:
  61. Visit http://hostname/ledger-smb/admin.pl, login with MYPASSWORD,
  62. Create datasets with user ledgersmb, superuser postgres
  63. Create users pointing to datasets.
  64. Congratulations, you have manually installed LedgerSMB 1.2.
  65. FTP INSTALLATION:
  66. ============================================================================
  67. If you control the server and have shell access, the
  68. instructions above are preferred over those given here.
  69. instead of those given here. This is simply a set of
  70. notes for those who must install on a shared server.
  71. If you do not have access to the server's configuration
  72. files install LedgerSMB in userspace by ftp'ing all the
  73. files to your server.
  74. a) untar ledger-smb in your private_html directory
  75. b) turn on script execution for the folder ledger-smb
  76. You can control this with an .htaccess file
  77. Options +ExecCGI
  78. DirectoryIndex login.pl
  79. c) protect the users directory with an .htpasswd file
  80. order allow,deny
  81. deny from all
  82. d) protect the templates directory with an .htpasswd file
  83. order allow,deny
  84. deny from all
  85. e) set up your PostgreSQL database and the tables. The basic
  86. procedure is specified above.
  87. You will most likely only have access to PostgreSQL with
  88. some other tools like pgadmin.
  89. TROUBLESHOOTING
  90. ===========================================================================
  91. Error: Access Denied in admin.pl
  92. Likely causes:
  93. 1) The password entered may not match the password set in step 6. You can
  94. repreat that step prior to the creation of user accounts as often as you
  95. wish.
  96. After the creation of user accounts, the commant to reset the admin password
  97. is:
  98. UPDATE users_conf SET password=mp5('MYPASSWORD') WHERE id =
  99. (select id FROM user WHERE username = 'admin');
  100. Of course, substitute 'MYPASSWORD' for your chosen password.
  101. 2) The central database may have been created with a different user than you
  102. are using for the connection and you may not have permission to access the
  103. required database entities. To correct this, assuming that the desired
  104. database username is ledgersmb, the following commands from psql:
  105. GRANT ALL ON users TO ledgersmb;
  106. GRANT ALL ON users_id_seq TO ledgersmb;
  107. GRANT ALL ON users_conf TO ledgersmb;
  108. GRANT ALL ON session TO ledgersmb;
  109. GRANT ALL ON session_session_id_seq TO ledgersmb;
  110. --------------------------------------------------
  111. Error: "No GlobalDBH Configured or Could not Connect"
  112. LedgerSMB 1.2 uses a dedicated connection to the central database for user
  113. authentication. When the attempt to connect to that database fails, the error
  114. message above is displayed. In this case, check the following parameters
  115. under the [globaldbh] of the ledger-smb.conf file.
  116. 1) DBUserName should match the database user you imported Pg-central as (if
  117. you followed the instructions above, that would be ledgersmb).
  118. 2) DBPassword needs to match the database password to used to connect to.
  119. You can test the above causes by running (from the command line):
  120. bash$ psql -U [DBUserName]
  121. password: [DBPassword]
  122. When you enter the password, it will not show up on the screen.
  123. The other line that you should pay attention to is the DBConnect line.
  124. Parameters in the form of name=value need to match those for your host. The
  125. following parameters need to be set correctly in that line:
  126. dbname=ledgersmb (or whatever database you imported Pg-Central.sql into).
  127. host=localhost (don't change this unless you know what you are doing!)
  128. port=5432 (don't change this unless you know what you are doing!)
  129. The full line should then be something like:
  130. DBConnect: dbi:Pg:dbname=ledgersmb;host=localhost;port=5432