psql [database name]then
psql [dbname] < /usr/share/ledgersmb/sql/upgrade/1.3-1.2.sql
By Erik Huelsmann
In summary: adding to or changing LedgerSMB can be extremely easy
For one of my businesses, I needed to create an application to store some data on the services and products we provide. Basically, there would be one central table with some references to a few other tables, mostly to provide (short) selection lists. Also, there's one bigger complexity, because we wanted to link to our customer data.
The customer data is all stored in LSMB, so, developing this database inside LSMB's database seemed like a logical choice.
1: Base Architecture Goals
The new architecture is designed to solve the following problems with the current codebase:
A) Maintenance difficulty. The current codebase is quite unstructured and difficult to maintain. 1.2.x has already been a bit of a mess due to the issues of fixing something one place and having it break something else.
See Getting Started (Developing) for up to date information
By Jeff Kowalczyk (jfkw)
I've been working on my local LedgerSMB deployment customization using the distributed version control system, git. I'm relatively new to git, but it's really helping me in the following areas: