Installation

I want to switch to LedgerSMB, but I have unpaid invoices. What to do?

Submitted by ehu on Mon, 06/29/2020 - 11:33

The general approach is to migrate invoices first, creating them as they exist in the current accounting solution. Then, differences with the intended balance can be calculated and the remainder posted at-once. For more comprehensive explanation see How do I migrate my existing books to LedgerSMB?

Installing latest LedgerSMB using Docker Compose

Submitted by ehu on Sat, 06/20/2020 - 04:48

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.

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

Submitted by ehu on 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.

Installing LedgerSMB 1.7

Submitted by ehu on Tue, 08/27/2019 - 12:37

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.

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:

Installing LedgerSMB 1.6

Submitted by ehu on Sat, 05/26/2018 - 05:33

Installation from tarballs

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

Upgrade to LedgerSMB 1.6 (from 1.5 or 1.4/starman)

Submitted by ehu on Sat, 05/26/2018 - 03:19

Upgrading tarball installations

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

  1. Upgrade the software
  2. Upgrade the company database

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

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.

Download

Submitted by Anonymous (not verified) on Sat, 04/01/2017 - 05:28

Maintained releases

The current stable release line is 1.7. For more information about older versions, see the FAQ item about supported releases. Versions 1.2 and older should no longer be used due to known security issues that cannot be resolved in that code base.