Aggregator

1.7.5 Released

21 hours 39 minutes ago
1.7.5 Released Security release No LedgerSMB_Team Fri, 12/13/2019 - 10:12 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.5/

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.7.5

  • Fix failure to save tax forms (#4252)
  • Fix failure to undo database edits when surrounding code fails (#4253)
  • Allow uploads of files with MIME types unavailable in the database (#1949)
  • Fix failure to render (AR/AP) aging report (#4259, #4260)
  • Separate authentication domains for setup.pl and login.pl (#4247)

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.7.5

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.5

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.7.5

These are the sha256 checksums of the uploaded files:

443e8b12eea99361dcb4479c2c62e8d54d54716f3755193df0735c1082ebfb32 ledgersmb-1.7.5.tar.gz
539caf56f8f4f8e4252b3bae7ac0ec618b4f481222308a85b27e05caa7feef2d ledgersmb-1.7.5.tar.gz.asc

Release 1.7
LedgerSMB_Team

1.7.4 Released

2 weeks 1 day ago
1.7.4 Released Security release No LedgerSMB_Team Fri, 11/29/2019 - 03:46 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.4/

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.7.4

  • Fix COGS failure when posting AP invoice reversal (#4218)
  • Include first transaction on account in reconciliation (#4221)
  • Fix error on reconciliation when no prior balance available (#4224)
  • Fix SQL write access error when posting fixed assets disposal (#4230)
  • Correctly calculate the tax basis amount even for 0% taxes ($4240)

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.7.4

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.4

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.7.4

These are the sha256 checksums of the uploaded files:

15a996fe9fd36ac28385ec975e1958727e70a398623015490b0dc5d1bd0dd31f ledgersmb-1.7.4.tar.gz
cda0574435ea777be22922c48dfe8a4ac659ba923d7d9283ea32e3626aad3aed ledgersmb-1.7.4.tar.gz.asc

Release 1.7
LedgerSMB_Team

1.6.16 Released

2 weeks 1 day ago
1.6.16 Released Security release No LedgerSMB_Team Fri, 11/29/2019 - 02:56 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.16/

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.16

  • Include first transsaction on account in reconciliation report (Erik H)
  • Fix COGS error when posting AP invoice reversal (Erik H)
  • Fix error in reconciliation in case no prior balance exists (Erik H)
  • Fix write access error thrown on fixed assets disposal (Erik H)
  • Correctly calculate tax basis amount even for 0% taxes (Erik H)

Erik H is Erik Huelsmann

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.6.16

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.16

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.6.16

These are the sha256 checksums of the uploaded files:

72527c660cbd839df06b7abbf16d15f093077c98aa2e1d098ccb738b6d558d01 ledgersmb-1.6.16.tar.gz
ba42bf5fef8733c4debf4a6d882e4cd92bdcf49685d408ce86e20f3f85f73aca ledgersmb-1.6.16.tar.gz.asc

Release 1.6
LedgerSMB_Team

1.5.30 Released

2 weeks 1 day ago
1.5.30 Released Security release No LedgerSMB_Team Fri, 11/29/2019 - 02:26 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.5.30/

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.5.30

  • Include first transsaction on account in reconciliation report (Erik H)
  • Fix COGS error when posting AP invoice reversal (Erik H)
  • Fix error in reconciliation in case no prior balance exists (Erik H)
  • Fix write access error thrown on fixed assets disposal (Erik H)
  • Correctly calculate tax basis amount even for 0% taxes (Erik H)

Erik H is Erik Huelsmann

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.5.30

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.5.30

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.5.30

These are the sha256 checksums of the uploaded files:

a19e0947a3181509e3543cfca29ae81b5323665889675e599ceaf4a4386b6b75 ledgersmb-1.5.30.tar.gz
a9dd176385498796fecbd90879b4902aa8971473475128a13b4ddaab7bc6b36b ledgersmb-1.5.30.tar.gz.asc

Release 1.5
LedgerSMB_Team

1.7.3 Released

4 weeks ago
1.7.3 Released Security release No LedgerSMB_Team Fri, 11/15/2019 - 12:13 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.3/

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.7.3

  • Fix regression in fixed assets module due to Multi Currency support (#4195)
  • Fix 'constraint not deferrable' error in fixed assets disposal (#4195)
  • Stop posting manual tax lines with zero amount and zero base amount (#4196)
  • Fix incorrect currency setup error on 'Update' in part screen (#4198)
  • Fix occasional COGS error on invoice posting (#4200)
  • Fix occasional COGS error on invoice reversal posting (#4213)
  • Fix regression with missing download links on reports (#4206)

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.7.3

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.3

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.7.3

These are the sha256 checksums of the uploaded files:

e007550265fd0ea3509b31bcd71950cb18664cc71cdf072df4b8b4f97a80f29f ledgersmb-1.7.3.tar.gz
b55ad96a32ccbbfeee6b78eb0a06beb86706cadd3678b1d6066fc6921cccd9bc ledgersmb-1.7.3.tar.gz.asc

Release 1.7
LedgerSMB_Team

1.6.15 Released

4 weeks ago
1.6.15 Released Security release No LedgerSMB_Team Fri, 11/15/2019 - 11:12 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.15/

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.15

  • Fix occasional COGS error on invoice posting (Erik H)
  • Fix occasional COGS error on invoice reversal posting (Erik H)
  • Fix failure on first reconciliation report for an account (Erik H)

Erik H is Erik Huelsmann

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.6.15

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.15

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.6.15

These are the sha256 checksums of the uploaded files:

80613c18f2a80401a636c1ef21456333b4087c2b5a8f46d4978cecbd75d2a0ae ledgersmb-1.6.15.tar.gz
4e3c25d4ccb694d238413b60441396dd5c150c1c99c117c44e621ff51efd737c ledgersmb-1.6.15.tar.gz.asc

Release 1.6
LedgerSMB_Team

1.5.29 Released

4 weeks ago
1.5.29 Released Security release No LedgerSMB_Team Fri, 11/15/2019 - 10:44 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.5.29/

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.5.29

  • Fix occasional COGS error on invoice posting (Erik H)
  • Fix occasional COGS error on invoice reversal posting (Erik H)
  • Fix failure on first reconciliation report for an account (Erik H)

Erik H is Erik Huelsmann

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.5.29

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.5.29

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.5.29

These are the sha256 checksums of the uploaded files:

ec8523647531361416db5fbc79b235d47f309bd532cff81c71540a36fa3414c4 ledgersmb-1.5.29.tar.gz
7c30f6f1e0520b1c3c897b4f0eebb266707db9d2ae8c8280a777754a91088565 ledgersmb-1.5.29.tar.gz.asc

Release 1.5
LedgerSMB_Team

1.7.2 Released

1 month 1 week ago
1.7.2 Released Security release No LedgerSMB_Team Sat, 11/02/2019 - 11:07 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.2/

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.7.2

  • Fix invoice screens crashing on manual tax with 0% tax rate (#4176)
  • Fix manual tax lines posted on current instead of transaction date (#4180)
  • Fix default currency invoice sometimes failing to save (#4184)
  • Fix SQL error in reversal of services in AP invoice (#4190)

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.7.2

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.2

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.7.2

These are the sha256 checksums of the uploaded files:

af7da4dea056080d9171271f917e7f568529b1c2d7316e3fe15637045d2ee4e5 ledgersmb-1.7.2.tar.gz
db923e2ba8deefee2b4750ebb42eb3727b01cf62ad3fa9f931932649c77bd872 ledgersmb-1.7.2.tar.gz.asc

Release 1.7
LedgerSMB_Team

1.6.14 Released

1 month 1 week ago
1.6.14 Released Security release No LedgerSMB_Team Sat, 11/02/2019 - 08:57 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.14/

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.14

  • Fix invoice screens crashing on manual tax with 0% tax rate (Erik H)
  • Fix manual tax lines posted on current instead of transaction date (Erik H)
  • Fix SQL error in reversal of services in AP invoice (Erik H)

Erik H is Erik Huelsmann

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.6.14

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.14

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.6.14

These are the sha256 checksums of the uploaded files:

6cbf98e32f5047185cd88f96d359e48d7fde350825bffb6bfa6bb8a843a8ec51 ledgersmb-1.6.14.tar.gz
957f9172014d5d2eb232fff9002e31114d8782bf99961221aacc027f73d09851 ledgersmb-1.6.14.tar.gz.asc

Release 1.6
LedgerSMB_Team

1.5.28 Released

1 month 1 week ago
1.5.28 Released Security release No LedgerSMB_Team Sat, 11/02/2019 - 08:25 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.5.28/

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.5.28

  • Fix invoice screens crashing on manual tax with 0% tax rate (Erik H)
  • Fix manual tax lines posted on current instead of transaction date (Erik H)
  • Fix SQL error in reversal of services in AP invoice (Erik H)

Erik H is Erik Huelsmann

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.5.28

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.5.28

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.5.28

These are the sha256 checksums of the uploaded files:

a20b3609d4b22c669a4cf2b0ce2bd55bcdd2a52a54ae9c9cbbcf80bf9fb0ea75 ledgersmb-1.5.28.tar.gz
935d779ebb7913e0482d3169c2240afe3b7de768b328774151fcf763e27955ab ledgersmb-1.5.28.tar.gz.asc

Release 1.5
LedgerSMB_Team

1.7.1 Released

1 month 3 weeks ago
1.7.1 Released Security release No LedgerSMB_Team Fri, 10/18/2019 - 06:11 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.1/

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.7.1

  • Generate unique names for backups
  • Fix tax checkmarks in contact screen sometimes being selected after save
  • Fix tax accounts inclusion in posted AR/AP transactions
  • Fix SQL error when running trial balance report
  • Fix assets and expenses with incorrect signs in GIFI balance and PnL

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.7.1

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.1

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.7.1

These are the sha256 checksums of the uploaded files:

b09ffd074ffc9c77f41ca06d8f5a94db23fa6723716c0e7278bd9eb1e3bbf9c5 ledgersmb-1.7.1.tar.gz
615fb3879d5156e6cd8c91ada1cec9c4b7ce78d52df1af4318793a2b68e3a72e ledgersmb-1.7.1.tar.gz.asc

Release 1.7
LedgerSMB_Team

1.6.13 Released

1 month 3 weeks ago
1.6.13 Released Security release No LedgerSMB_Team Fri, 10/18/2019 - 05:19 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.13/

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.13

  • Generate unique names for backups (Erik H)
  • Fix incorrect tax checkmarks in contact screen after save (Erik H)
  • Fix tax accounts inclusion in posted AR/AP transactions (Erik H)

Erik H is Erik Huelsmann

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.6.13

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.13

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.6.13

These are the sha256 checksums of the uploaded files:

681e6920d7a0c8c6d30f59b04d4ba4730d9c9f15d910e39b4e0b42adad6b6f43 ledgersmb-1.6.13.tar.gz
f6c68a706d8198a2d1987338324b95ef62d0df382a617759859681122e777cf7 ledgersmb-1.6.13.tar.gz.asc

Release 1.6
LedgerSMB_Team

1.5.27 Released

1 month 3 weeks ago
1.5.27 Released Security release No LedgerSMB_Team Fri, 10/18/2019 - 04:50 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.5.27/

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.5.27

  • Fix incorrect tax checkmarks in contact screen after save (Erik H)

Erik H is Erik Huelsmann

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.5.27

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.5.27

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.5.27

These are the sha256 checksums of the uploaded files:

655309c5e88daba8a3a502ac9f1e2a362edba06a442cb48e27c57c160fe06131 ledgersmb-1.5.27.tar.gz
ad7bb1ed56bef418f9066445bc0107238d9606e56ee1ccf67575f4d9a5d25ef2 ledgersmb-1.5.27.tar.gz.asc

Release 1.5
LedgerSMB_Team

1.7.0 Released

2 months 1 week ago
1.7.0 Released Security release No LedgerSMB_Team Fri, 10/04/2019 - 10:18 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.0/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.

This release brings support for multiple exchange rates per currency
per day -- before, only a single rate per currency was supported.
Additionally, a lot of effort went into quality assurance and code
cleanup.

The changes to the database schema to add the improved multicurrency
support are quite extensive. A lot of checks have been implemented to
assure correct migration. However, it's strongly recommended to create
a backup before migrating. The migration procedure may ask questions
when insufficient data is in the database to complete the upgrade. In
case of doubt about what to answer, please contact the users mailing
list at users@lists.ledgersmb.org.

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.7.0

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.0

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.7.0

These are the sha256 checksums of the uploaded files:

384e7697fc23c1f8a418d576c121adbf56aa67e9254aa043e35b0b4b1caefef3 ledgersmb-1.7.0.tar.gz
08289470d6c1204a83f9ab41d42aace7098179585d4b2bfad5bea7c8a19b8af1 ledgersmb-1.7.0.tar.gz.asc

Release 1.7
LedgerSMB_Team

1.6.12 Released

2 months 2 weeks ago
1.6.12 Released Security release No LedgerSMB_Team Sun, 09/29/2019 - 12:35 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.12/

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.12

  • Work around unloadable backups being dumped on some PostgreSQL version combinations (Erik H)

Erik H is Erik Huelsmann

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.6.12

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.12

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.6.12

These are the sha256 checksums of the uploaded files:

85aaa93c90867d2707a59e8ab5290e666a8ac260f56304cdb2c0486688ef50e9 ledgersmb-1.6.12.tar.gz
943b1cecbcfb1dcce3450f623edc7973ce08e3241256c0f383a80ccde605aad1 ledgersmb-1.6.12.tar.gz.asc

Release 1.6
LedgerSMB_Team

1.5.26 Released

2 months 2 weeks ago
1.5.26 Released Security release No LedgerSMB_Team Sun, 09/29/2019 - 12:25 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.5.26/

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.5.26

  • Work around unloadable backups being dumped on some PostgreSQL version combinations (Erik H)

Erik H is Erik Huelsmann

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

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.5.26

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.5.26

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.5.26

These are the sha256 checksums of the uploaded files:

556494d2da5bee02bf632ded0ddf0cd8dc22023700ed8e575d75dc6540220b3a ledgersmb-1.5.26.tar.gz
a9247de3216c2e19066a029c454a0ba52e025399adb3d5674fd015bd1802dfa1 ledgersmb-1.5.26.tar.gz.asc

Release 1.5
LedgerSMB_Team

Why does the acc_trans table have fewer lines after upgrading to 1.7?

3 months 2 weeks ago
Why does the acc_trans table have fewer lines after upgrading to 1.7? ehu Tue, 08/27/2019 - 13:11

Short answer: Due to differences in the database schema in relation to storing foreign currency transactions.

Long answer: The database schema before 1.7 required 2 database rows in the acc_trans table to store functional currency and foreign currency amounts. As of 1.7, the schema stores these two amounts - which relate to the same journal line - into one database row. When migrating data from the old schema to the new one, the migration routine tries hard to identify pairs of rows which can be combined into a single row in the new schema.

Release 1.7 FAQ Category Installation Topic Installation Upgrading Upgrade
ehu

Installing LedgerSMB 1.7

3 months 2 weeks ago
Installing LedgerSMB 1.7 Installation from tarballs

This page contains the comprehensive version with the installation instructions for LedgerSMB 1.7 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.

These are not the Quick start instructions, but instructions for setting up a full production system. Also, please note that if you're in a position to use LedgerSMB's Docker images, or packages for your Unix/Linux distribution, using those will be far quicker and easier than following the instructions below.

Please note that installation of version 1.5 and up is completely different from the installation of versions 1.4 or earlier: This version uses Plack to handle integration with front-end web servers. This means LedgerSMB can now be run in combination with many web servers, including (but not limited to):

It's no longer possible to run LedgerSMB as set of CGI scripts. This should not be a big concern, since Plack allows plugging LedgerSMB into Apache using mod_fcgid, mod_fastcgi or mod_proxy all of which have been available for versions 2.0 and up.

Feel free to log in and share your experiences in the comments at the end of the article.

System requirements

Requirements are documented on the system requirements page.

Client

There are no specific requirements for LedgerSMB clients (web browsers) other than that they should have JavaScript enabled and be able to run Dojo 1.15.

A broad range of browsers is supported (Chrome, FireFox, Opera, ...), including Microsoft Internet Explorer (10 or newer) and Microsoft Edge.

Browsers explicitly not supported are:

  • Lynx
  • w3m
  • IE9 or earlier
Unpacking the release tarball

According to the Filesystem Hierarchy Standard, both /usr/local/ledgersmb and /opt/ledgersmb could be chosen as install locations. Unpack the tarball by running (as "root" user):

# tar xf ledgersmb-1.7.x.tar.gz --directory /usr/local/ Installing the LedgerSMB Perl module dependencies

Please note that some distributions (e.g. Fedora) do not by default install all core modules, but rather, install a subset. LedgerSMB doesn't list core modules as dependencies as they should be available.

The instructions below assume all dependencies will be installed from CPAN. It is however possible to install most modules from distribution repositories. The Docker image can be consulted for an example.

# Installation of LedgerSMB Perl dependencies from CPAN
cpanm --quiet --notest --with-feature=starman --installdeps /usr/local/ledgersmb/

Then, there are a number of features which need additional modules.
The above command includes the Starman Feature which is required for most installations.
The modules required for each feature can be installed by appending "--with-feature=" to the above command line.

These features are supported:

Feature Description latex-pdf-ps Enable PDF and PostScript output
Note: In order to make use of this functionality, the server must also have 'latex' or 'xelatex' installed. On many distributions, these packages are called 'texlive-latex' and 'texlive-tetex' respectively. latex-pdf-images Image size detection for PDF output starman Starman Perl/PSGI (standalone) web server openoffice OpenOffice.org document output edi (EXPERIMENTAL) X12 EDI support

 

# Installation of LedgerSMB Perl dependencies directly from CPAN
# With Starman and PDF & Postscript output

cpanm --quiet --notest --with-feature=starman --with-feature=latex-pdf-ps \
--installdeps /usr/local/ledgersmb/

Configuring the PostgreSQL server

There are only two requirements for the PostgreSQL database server. This section instructs how to configure an pre-installed PostgreSQL installation to meet those requirements. It's assumed that the LedgerSMB server and PostgreSQL are being run on the same system. The requirements to meet are:

  1. A database administrator user (in PostgreSQL called a 'role') for creation and administration of LedgerSMB company databases
  2. Authorization setup so the database administrator can log into the database through LedgerSMB's 'setup.pl' program
Creating the company database administrator account

The database administrator user account needs to have at the bare minimum:

  • The right to create databases (CREATEDB)
  • The right to create roles (CREATEROLE)
  • The right to log in (LOGIN)
  • A password to authenticate logins

The following command issued as root user, creates a user named "lsmb_dbadmin" (which isn't a super user):

# su - postgres -c 'createuser -S -d -r -l -P lsmb_dbadmin'
Enter password for new role: ************
Enter it again: ************

Configuring database access rights

PostgreSQL takes its access configuration through a file called 'pg_hba.conf'. The location of this file may differ per distribution:

  • Debian derivatives: /etc/postgresql///pg_hba.conf
  • RedHat derivatives: /var/lib/pgsql//data/pg_hba.conf

On most systems, this file has four effective lines:

local   all             postgres                                peer
local   all             all                                     peer
host    all             all             127.0.0.1/32            peer
host    all             all             ::1/128                 peer

These lines mean that each system user can connect to the database system with an equally named database user; the connecting source doesn't make a difference: unix and TCP/IP sockets have the same configuration.

The LedgerSMB software needs to be able to connect to the database system as 'lsmb_dbadmin' or as a LedgerSMB user, not as the user that runs the server process. The new content should look like:

local   all             postgres                         peer
local   all             all                              peer
host    all             postgres         127.0.0.1/32     reject
host    all             postgres        ::1/128      reject
host    postgres,template0,template1   lsmb_dbadmin         127.0.0.1/32     md5
host    postgres,template0,template1   lsmb_dbadmin         ::1/128      md5
host    postgres,template0,template1   all          127.0.0.1/32     reject
host    postgres,template0,template1   all          ::1/128      reject
host    all             all             127.0.0.1/32     md5
host    all             all             ::1/128          md5

This configuration takes advantage of the fact that each connection method (unix sockets vs TCP/IP sockets/addresses) can be separately configured. While the default connection method of the 'psql' tool is to connect over the 'local' (unix socket method), the default connection method for LedgerSMB is to use 'localhost' (127.0.0.1/32 or ::1/128).

The above configuration means that the user 'postgres' can't be used any longer to connect from 'localhost', no user can connect to the 'postgres' database through 'localhost' [reject] and all other combinations of users and database names need password authentication [md5].

Notes:

  1. PostgreSQL matches the lines first to last and uses the first matching line, so the order of the lines is very importance.
  2. For more information about the pg_hba.conf configuration options, see the PostgreSQL pg_hba.conf documentation
  3. The databases 'template1' and 'template0' are system databases available in every cluster; this configuration blocks those for access from LedgerSMB as well.

After reconfiguring pg_hba.conf, the PostgreSQL service needs to be restarted. this works with one of the following commands (depending on your distribution):

# restarting postgresql service (as root)
# service postgresql restart
# - or -:
$ service postgresql- restart

Verifying database access

To verify access for the database admin user 'lsmb_dbadmin', an accessible database - not named 'postgres', 'template0' or 'template1' - is required. On new installs, these are the only databases. So the next example creates one. Here's how to verify the setup:

# Verify access configuration (run as root)
$ su - postgres -c 'createdb lsmb_access_test_db'
$ psql -h localhost -U lsmb_dbadmin -d lsmb_access_test_db -c "select version()"
PostgreSQL 9.4.7 <--- this line indicates success("9.4.7" is just an example version number)
$ su - postgres -c 'dropdb lsmb_access_test_db'

Configuring a web server

Regardless of your web server setup, configuration of an "application server" is required. The application server used with LedgerSMB can be any PSGI compatible server. The default application server is Starman, which is widely considered the fastest available. The Starman server process lives behind a reverse proxy. While Starman deals specifically with those HTTP requests which require "application logic", all other requests (mostly static content, such as images or CSS) are dealt with by the proxy.

Configuring the Starman application server

Depending on the distribution, a startup method must be installed; this can be one of:

  • SysV init script
  • Upstart configuration
  • Systemd configuration

At the time of writing, the only configuration that comes with LedgerSMB's tarball is the systemd configuration. The following common setup is required regardless of the system used to manage services on the target system.

To support priviledge separation, the Starman server should be running as a user which meets these criteria:

  • Not the same user as the web server
  • Does not have write access to the LedgerSMB directories

To that extent, identify an existing (unused) system user, or create one with this command:

# create 'ledgersmb' user for Starman server to run
$ useradd -d /non-existent -r -U -c "LedgerSMB/Starman service system user" ledgersmb

Configuring systemd for Starman

In the directory conf/systemd/ from the tarbal, there is a preconfigured systemd service file, which needs to be copied into place. In case you decided to install dependencies into a local::lib, the service file needs to be edited to set a PERL5LIB environment variable before you can succesfully start the service.

# 'copy' systemd service configuration, enable and start
$ sed -e "s#WORKING_DIR#$PWD#" conf/systemd/ledgersmb_starman.service \
| sudo tee /etc/systemd/system/ledgersmb-starman.service
$ systemctl enable ledgersmb-starman
$ service ledgersmb-starman start

Note that the above assumes that the commands are being run from the root of the unpacked tarball. It also assumes that the tarball has been unpacked at its installation path.

To verify that the service started up correctly, run:

# verify that the Starman/LedgerSMB server started correctly
$ journalctl -u ledgersmb-starman.service --since="today" -l -e

Configuring a reverse proxy

For a quick test-run or demo setup running on localhost only, configuration of a proxy isn't mandatory. However, for a production setup with LedgerSMB being network or even web-exposed, it's ill-advised to run without the reverse proxy for - at least - the following reasons:

  • The proxy can serve static content [much] more efficiently (performance)
  • The proxy can support HTTP/2 which multiplexes requests (performance)
  • The proxy guards Starman against public exposure (security)
  • The proxy adds TLS (security)

With TLS certificates being completely free these days through Let's Encrypt, and only a few dollars for the simplest of certificates from commercial vendors, there's really no reason not to secure traffic to the server. Further documentation below assumes you have such a certificate. As for getting Let's Encrypt certificates, use their Getting Started guide.

For simplicity, only the configuration of nginx as a reverse proxy is documented here.

Configuring nginx

The tarball contains an example virtual host configuration file to set up a reverse proxy with nginx. It needs to be included in the 'http { }' block in your nginx configuration. On Debian derived systems, this is done by copying the file to /etc/nginx/sites-available/ledgersmb.conf. On RedHat/Fedora derivatives, the copying goes to /etc/nginx/conf.d/ledgersmb.conf. After editing the file, replacing the following variables:

  • Same replacement as before
  • SSL_CERT_FILE
    Should be where your certificate file is stored; probably /etc/certs/your_host.example.com.pem
  • SSL_KEY_FILE
    Probably the same as the SSL_CERT_FILE, but with '.key' extension
  • YOUR_SERVER_NAME
    If nothing else, should be replaced by the output of the command 'hostname -f'

NOTE: by default snakeoil certificates will be used by at least our nginx sample config files.
These certificates are locally created and will normally require your browser clients to override something before they can be used.

On Debian derivatives, activate this file after it has been edited, using:

# On Debian/Ubuntu/Mint activate the virtual host
$ ln -s /etc/nginx/sites-available/ledgersmb.conf /etc/nginx/sites-enabled/

On RedHat/Fedora derivatives, no symlinking is necessary: the configuration is active immediately. Now, verify that the configuration is acceptable:

# (Re)start nginx service to make nginx reconfigure itself and validate configuration
$ service nginx restart

Configuring LedgerSMB

The tarball has a default LedgerSMB configuration file conf/ledgersmb.conf.default. Install the configuration file with:

# Install the default ledgersmb.conf configuration file
$ cp conf/ledgersmb.conf.default ledgersmb.conf

That is it.

In case the in-app e-mail feature is going to be used, check the values in the [mail] section and optionally adjust for the mail setup of the target system.

Next steps

Now follow the instructions in the "Prepare LedgerSMB for first use" guide.

ehu Tue, 08/27/2019 - 12:37 Topic Installation Release 1.7
ehu

Upgrade to LedgerSMB 1.7 (from 1.6 or 1.5)

3 months 2 weeks ago
Upgrade to LedgerSMB 1.7 (from 1.6 or 1.5) Upgrading tarball installations

There are two steps to upgrading a LedgerSMB 1.5.x/1.6.x to 1.7:

  1. Upgrade the software
  2. Upgrade the company database

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

Attention! Due to the complexity in the upgrade related to the "multiple currency rate support" (MC support), it's of the greatest importance that you create a backup of your data before starting the upgrade. In setup.pl, for every database, you need to download a database backup and a roles backup.

These steps also apply when upgrading a 1.4 installation running Starman. To upgrade 1.4 installations not running on Starman, or to upgrade from earlier versions, please see Upgrading to Ledgersmb 1.5. Note that the default configuration for 1.4 runs CGI, not Starman.

Again, before upgrading: backup your databases.

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

Upgrading the software

These are the steps to follow, assuming an installation from tarball:

  • Stop the LedgerSMB application server (e.g. Starman) $ sudo service starman-ledgersmb stop
  • Back up the old software by moving it out of the way (assuming you installed in /usr/local/ledgersmb): $ sudo mv /usr/local/ledgersmb /usr/local/ledgersmb.backup
  • Untar the tarball into /usr/local/ledgersmb: $ sudo tar xf ledgersmb-1.7.x.tar.gz --directory /usr/local
  • Copy the configuration file from the old installation: $ sudo cp /usr/local/ledgersmb.backup/ledgersmb.conf /usr/local/ledgersmb/
  • Upgrade the LedgerSMB Starman SysV or systemd scripts (the new scripts can be found in /usr/local/ledgersmb/conf/systemd/ ) $ sudo cp /usr/local/ledgersmb/conf/systemd/ledgersmb_starman.service /etc/systemd/system/ledgersmb.service $ sudo systemctl daemon-reload
  • Start the LedgerSMB application server again (Starman example given, as before): $ sudo service starman-ledgersmb start
Upgrading the company database

After the software has been upgraded, the company database(s) must be upgraded. Without this step, a "Database version mismatch" error will be generated on user-login.

To upgrade the company database from the Web UI, navigate to the setup.pl page (e.g. when you're hosting your LedgerSMB on https://localhost/ and normally log in through https://localhost/login.pl, navigate to https://localhost/setup.pl). Log into setup.pl with the database admin credentials (the "lsmb_dbadmin" user, if you followed the installation instructions).

After login, setup.pl will show a screen with the following at the top:

 

Logged in as lsmb_dbadmin
LedgerSMB 1.6 db found
Rebuild/Upgrade?

By clicking the "Yes" button, the company database upgrade process will be executed. This is an interactive process which consists of a number of steps. Each step of the upgrade process consists of two phases. In the first phase, the application will verify that the data as available in the database has sufficient quality to be upgraded. If this isn't the case, the user will be asked for input to address quality problems. Once data has acceptable quality, the actual database upgrade will be executed. When all steps in the upgrade have been successfully executed, setup.pl will report complete migration. The database is now available for use again.

Repeat this process for all company databases.

For power-users who need to do scripted upgrades, there's a scripting API available which replaces the interactive process with pre-defined inputs. Contact the developers mailing list for more information.

 

ehu Tue, 08/27/2019 - 12:02 Topic Installation Release 1.5 1.6 1.7
ehu

1.7 release notes

3 months 2 weeks ago
1.7 release notes What's new in LedgerSMB 1.7
  • Multiple exchange rates per currency per date
  • Deletion of template transactions
  • Transaction date now part of the purchase history report
  • UI allows addition and removal of custom `account_link` flags
New features Multiple exchange rates per currency per date

Before 1.7, for every currency, there would be a single associated 'buy' rate (used for sales transactions) and a single associated 'sell' rate (used for puchase transactions) and some half-baked solution for foreign currencies in GL transactions. This could cause problems when using foreign currency transactions with different banks (using different rates) on the same day. Similarly did this cause problems reversing fx transactions on any other date than their posting date (which didn't combine well with closed periods). Starting 1.7, there are no 'buy' and 'sell' rates anymore: every sales or purchase transaction has its own exchangerate. Next to that, there's a facility to hold advisory rates per currency per day.

Deletion of template transactions

In prior versions, template transactions could be created and used, but not deleted. This omission has been addressed in this release.

Transaction date now part of the purchase history report

The purchase history report has been extended by one column: the date of the purchase transaction.

UI allows addition and removal of custom 'account_link' flags

When developing extensions to LedgerSMB (such as WebService::HMRC::VAT), accounts often need to be flagged into custom categories. In prior versions there was support for these categories, but no UI to assign/deassign accounts into these categories. This omission has been taken care of in this release.

Other user-visible changes

There are no other user-visible changes. For a complete list including technical changes and dependency updates, see our Changelog.

Known issues
  • Single-day time-card entry is broken (since 1.4); weekly entry works though
ehu Tue, 08/27/2019 - 06:45 Topic release notes Release 1.7
ehu