The LedgerSMB development team is happy to announce the first
release of a new release branch: 1.8.0. This series features
a wide variety of new features, improvements, bug fixes and
cleanup. To name a few:
Installation from tarballs
This page contains the comprehensive version with the installation instructions for LedgerSMB 1.8 targetting a production installation from release tarballs and deals with these steps:
- Installing the LedgerSMB Perl module dependencies
- Configuring the PostgreSQL server
- Configuring a webserver
- Configuring LedgerSMB
If you already have all of the above, please proceed to the "Preparing for first use" guide.
Yes. LedgerSMB has a mechanism called "Account headings". The headings are the opposite of what Intuit explains about Quickbooks for their subaccount support: Quickbooks splits an account into multiple and aggregates those new accounts into the old one for reporting. To achieve the same in LedgerSMB, you create multiple accounts and one or more headings. LedgerSMB then aggregates the totals of the accounts per heading. The system used by LedgerSMB closely resembles what MYOB describes about their accounts and headers.
Company database upgrades are supported all the way back from 1.4 directly to 1.8, using the 1.8 software. Company database upgrades from 1.3 and 1.2 are also supported, but due to the different nature of the upgrade process are called "migrations". The important difference being that when doing a migration, a copy of the data is being created in the 1.8 structure, while upgrades adjust the existing structure for 1.8.
In preparation of the final release of LedgerSMB 1.8, the release branch has been created for a period of stabilization. In order to release the most stable version released by the project ever released, a preview version was published earlier today: 1.8.0-beta3.
By far the fastest procedure for installing LedgerSMB is by using the published Docker images: Being an ERP, there are many dependencies to be installed and all of them are included in the images, with the exception of the required PostgreSQL database. There are two ways to provide the PostgreSQL functionality: by setting up a separate PostgreSQL server or by using a PostgreSQL-providing Docker container.
In preparation of the final release of LedgerSMB 1.8, the release branch has been created for a period of stabilization. In order to release the most stable version released by the project ever released, a preview version was published earlier today: 1.8.0-beta1.
What's new in LedgerSMB 1.8
- Authentication and session storage using encrypted cookies
- In-database logos and images upload and template support
- Downloadable reports now stored in the database for customization
- New e-mail configuration in ledgersmb.conf
- Reconciliation takes payments as first-order transactions
- Import of OFX bank statement files for reconciliation
Authentication and session storage using encrypted cookies
This release switches to using encrypted cookies instead of HT