Installation

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.

Upgrading LedgerSMB 1.5.x to 1.5.y

Submitted by ehu on Tue, 02/28/2017 - 08:38

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 Fri, 12/23/2016 - 13:27

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!

Installing LedgerSMB 1.5

Submitted by ehu on Sun, 12/27/2015 - 05:54

This content is outdated and kept here for reference only!

This page contains the comprehensive version with the installation instructions for LedgerSMB 1.5 (as of 1.5.0) 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, proceed to the "Preparing for first use" guide.

System requirements

Hardware requirements

The hardware required to run LedgerSMB greatly depends on the number of users. However, with a small number of users (up to 10 or so), a 32bit server with 512MB to 1GB of memory (including Linux Server OS) and just a few hundred MB of storage (excluding OS) should be enough to get good performance.
For a 64bit server, you probably need 1GB to 2GB of memory, but otherwise the requirements are the same.