1.6

How do I restore my data?

Submitted by ehu on Mon, 05/13/2013 - 13:04

Assuming you have followed the How Do I Backup My Data instructions, you can restore your database as follows...

1) Restore the roles

$ psql -h [database host] -U [database admin user] < [roles backup file]

For example:

$ psql -h localhost -U lsmb_dbadmin < lsmb-roles.sqlc

2) Create a new database to restore into

$ psql -h [database host] -U [database admin user] -c 'CREATE DATABASE [new company name]'

For example:

How do I backup my data?

Submitted by Anonymous (not verified) on Tue, 11/29/2011 - 19:44

Log in to the the 'setup.pl' administrative interface, using your ledgersmb database admin user (usually "lsmb_dbadmin" or "postgres"). The default address for setup.pl is http://localhost/ledgersmb/setup.pl.

There are 2 buttons:

  • Backup database (parts, customers, accounting records, etc)
  • Backup roles (your login accounts and rights)

One creates a backup of the content of your database. The other creates a backup of the roles.

1.6.10 Released

Submitted by LedgerSMB_Team on Sun, 01/20/2019 - 07:37

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.6.10

1.6.9 Released

Submitted by LedgerSMB_Team on Wed, 12/26/2018 - 03:30

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
Please note that this version fixes an bug where unsuspecting users
could make accounting mistakes: sales taxes not correctly included
in the amount due for purchase invoices. The bug is present in all
1.5 version prior to 1.5.24 and all 1.6 releases prior to 1.6.9.
Also note that AP Transactions are not affected by this bug and
have been working correctly in 1.5 and 1.6 releases.

1.6.8 Released

Submitted by LedgerSMB_Team on Sun, 12/16/2018 - 11:02

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
Please note that this release fixes a data loss issue present in
all prior 1.6 versions and all versions before 1.5.23. Affected
by this bug are those using both orders and invoices in combination
with shipping information. If you don't use both (or just one of
them), you're not affected.
This release contains the following additional fixes and improvements:

Changelog for 1.6.8

1.6.7 Released

Submitted by LedgerSMB_Team on Fri, 12/14/2018 - 10:17

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.6.7

1.6.6 Released

Submitted by LedgerSMB_Team on Sun, 10/14/2018 - 13:55

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.6.6

1.6.5 Released

Submitted by LedgerSMB_Team on Sun, 09/16/2018 - 13:33

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fix:

Changelog for 1.6.5

  • Update Dojo to 1.13.3-pre; previous update broke file uploads (Erik H, #3799)

Erik H is Erik Huelsmann

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.6.5/README.md

1.6.4 Released

Submitted by LedgerSMB_Team on Sat, 08/25/2018 - 06:07

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.6.4

Upgrading LedgerSMB 1.6.x to 1.6.y

Submitted by ehu on Fri, 07/27/2018 - 08:19

Upgrading tarball installations

There are two steps to upgrading a LedgerSMB 1.6.x installation to 1.6.y (x smaller than y):

  1. Upgrade the software
  2. Upgrade the company database

The last step has to be executed for each company database that's set up.

Note that all the steps below are prefixed with the 'sudo' command, but these can be executed as 'root' directly as well.

Upgrading the software

This is by far the easiest part. These are the steps to go through, assuming an installation from tarball:

Subscribe to 1.6