summaryrefslogtreecommitdiff
path: root/INSTALL
blob: ae2ba808991d6cec2478416241a00eddca545066 (plain)
  1. Installing LedgerSMB 1.2
  2. This document contains information on how to upgrade from earlier versions of
  3. LedgerSMB or SQL-Ledger. This upgrade is a major revision and may not go
  4. smoothly. We recommend that the reader start by reading the section on manual
  5. installation and then start by trying the automated means mentioned later.
  6. Also this document assumes that the reader is already familiar with the release
  7. notes. If you have not already done so, please read the release_notes file in
  8. the doc/ directory.
  9. MANUAL UPGRADE:
  10. ===============================================================================
  11. 1) Untar in desired location.
  12. 2) Check New Dependencies
  13. The Build.PL script can be used to test for unmet dependencies and run other
  14. tests. It doesn't install anything yet, but it will tell you what you are
  15. missing. To check for dependencies, run "perl Build.PL" from the command line.
  16. Missing dependencies can generally be installed via a Linux distributor's
  17. package manager or by CPAN.
  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) Install database
  27. a) cd to the sql/legacy/ directory of the new ledger directory
  28. b) run "psql" with appropriate options to connect to your database.
  29. c) Note the db version by running the following query:
  30. "SELECT version FROM defaults;"
  31. d) Run the SQL upgrade scripts in order starting with the one whose name
  32. begins with "Pg-database" (each of these scripts will upgrade to
  33. the next database version which is also identified in the file name).
  34. Note that this will create three tables that may not actually be used depending
  35. on your setup: users, users_conf, and session. In general if you have multiple
  36. datasets, these tables will only be used in one.
  37. 4) Decide where to put the user/session management tables. In general, we
  38. recommend as follows:
  39. a) Single dataset installations should use the user tables in the dataset.
  40. b) Multicompany installations should use user tables in a separate dataset
  41. from any accounting data.
  42. If you need to create another dataset, you can create the db and import the
  43. sql/Pg-central.sql file into it.
  44. 5) Set the admin password:
  45. a) From psql, determine what admin password you wish to use. Then type:
  46. "update users_conf set password = md5('my_password');"
  47. Naturally you would use your password instead of my_password.
  48. Congratulations, you have manually installed LedgerSMB 1.2.