Installation

Installing latest LedgerSMB using Docker Compose

Submitted by ehu on

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

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

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

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

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.

Upgrading LedgerSMB 1.5.x to 1.5.y

Submitted by ehu on

Upgrading tarball installations

There are two steps to upgrading a LedgerSMB 1.5.x installation to 1.5.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:

Upgrading to LedgerSMB 1.5

Submitted by ehu on

Before starting to update to 1.5, the following are differences to be aware of between 1.4 and 1.5:

  • JavaScript in the browser
  • Additional data constraints
  • PSGI / Apache configuration
  • Printed document templates (e.g. invoice templates)
  • Database schema maintenance

See below for explanations of each of these differences.

 

Important note: before trying to migrate your database to a new version of LedgerSMB, create a backup of the database!