summaryrefslogtreecommitdiff
path: root/INSTALL
blob: 3fcb101352d245cc1ab4f24b9496b916b7f7d5cc (plain)
  1. Installing LedgerSMB 1.3
  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. MANUAL INSTALL:
  9. ===============================================================================
  10. 1) Untar in desired location.
  11. 2) Check Dependencies
  12. The Build.PL script can be used to test for unmet dependencies and run other
  13. tests. It doesn't install anything yet, but it will tell you what you are
  14. missing. To check for dependencies, run "perl Build.PL" from the command line.
  15. Missing dependencies can generally be installed via a Linux distributor's
  16. package manager or by CPAN. (Build.PL itself uses Module::Build, which is
  17. available in packages like perl-Module-Build or libmodule-build-perl.)
  18. Once this is done and dependencies are satisfied, you can check to see whether
  19. the installation nominally works by running "./Build test" from the command
  20. line. The test suites currently check to make sure all the perl modules load
  21. and that a number of numeric tests are passed.
  22. Dependencies which are recommended are needed only for specific functionality
  23. and may not be required in all circumstances. These include:
  24. * Net::TCLink for credit card processing in a POS environment
  25. * Parse::RecDescent for the CLI script host
  26. 3) Decide where to put the user/session management tables. In general, we
  27. recommend as follows:
  28. a) Single dataset installations should use the user tables in the dataset.
  29. b) Multi-company installations should use user tables in a separate dataset
  30. from any accounting data.
  31. 4) Install Tsearch2 Full Text indexing engine for PostgreSQL (not optional)
  32. a) If you installed PostgreSQL from source, Tsearch2 is in contrib.
  33. b) If you installed from package, you will need the package
  34. postgresql-contrib or equivalent
  35. c) Use psql to apply the tsearch2.sql to template1. The file is normally
  36. installed to
  37. /usr/share/postgresql/contrib/tsearch2.sql or
  38. //usr/share/postgresql/<version>/contrib/tsearch2.sql
  39. 5) Install tablefunc.sql for PostgreSQL (not optional)
  40. See notes in 4 above for location of script and apply to template1.
  41. 6) Install pg_trgm.sql into database or template1.
  42. See notes in 4 above for location of script. Apply to template1.
  43. 7) Create central database
  44. a) create the ledgersmb role (optional)
  45. b) create the ledgersmb database (if using a multi-company central db)
  46. c) cd to the sql/ directory of the new ledger directory.
  47. d) load the Pg-database.sql script into ledgersmb or your database.
  48. 8) Set the admin password:
  49. From psql, determine what admin password you wish to use. Then type:
  50. "update users_conf set password = md5('my_password');"
  51. Naturally you would use your password instead of my_password.
  52. 9) Edit the ledgersmb.conf file as appropriate.
  53. Congratulations, you have manually installed LedgerSMB 1.3.