Aggregator

1.10.4 Released

3 weeks 6 days ago
1.10.4 Released Security release No LedgerSMB_Team Sun, 10/30/2022 - 06:36 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.10.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.10.4

* Fix AR/AP transactions posted, not saved, with separation of duties (#6932)

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

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

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

Or pulled from the GitHub Container Registry
$ docker pull ghcr.io/ledgersmb/ledgersmb:1.10.4

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

These are the sha256 checksums of the uploaded files:

f3c3f26aa67051df74021eaf7432eaa682cc7bf605604eb387511a05e1956b7a ledgersmb-1.10.4.tar.gz
1c5b77fd9eb7caf6da41f26aaac363dea526441e19ebcc37be6ea0b325713dc9 ledgersmb-1.10.4.tar.gz.asc

Release 1.10
LedgerSMB_Team

1.10.3 Released

4 weeks ago
1.10.3 Released Security release No LedgerSMB_Team Sun, 10/30/2022 - 02:53 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.10.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.10.3

* Fix 'New' button on invoice and transaction screens (#6893)
* Fix UTF-8 character handling calling into old code (#6897)
* Fix database upgrades based on demo dataset (#6879)
* Remove stray double quote and curly character in purchase invoice (#6905)
* Fix regression preventing cross-yearend pnl reporting (#6386)
* Catch and report errors from updating pages (#6906)
* Fix invoice and order screens breaking on 'min empty lines' > 1 (#6911)

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

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

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

Or pulled from the GitHub Container Registry
$ docker pull ghcr.io/ledgersmb/ledgersmb:1.10.3

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

These are the sha256 checksums of the uploaded files:

6d0c15594de9b562030a35700eabbf7724a5a84cf4148955fd17c3ecd6ad4726 ledgersmb-1.10.3.tar.gz
b35064821a8767ad066c78a7b46c81ca49fbe53a73dbf15bd13382add54fb182 ledgersmb-1.10.3.tar.gz.asc

Release 1.10
LedgerSMB_Team

1.9.19 Released

4 weeks ago
1.9.19 Released Security release No LedgerSMB_Team Sun, 10/30/2022 - 02:52 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.9.19/

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

* Fix UTF-8 character handling calling into old code (#6998)
* Fix regression preventing cross-yearen PNL reporting (#6386)
* Fix invoice and order screens breaking on 'min empty lines' > 1 (#6926)

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

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

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

Or pulled from the GitHub Container Registry
$ docker pull ghcr.io/ledgersmb/ledgersmb:1.9.19

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

These are the sha256 checksums of the uploaded files:

2d7e2f6d45eeae338b9b8c990dca32116ad41fa8e8c7f0464dcc0e342225e57a ledgersmb-1.9.19.tar.gz
2294d3d997de867790d1844714f06a67f00db7f5eda844e0fd91950876458490 ledgersmb-1.9.19.tar.gz.asc

Release 1.9
LedgerSMB_Team

1.10.2 Released

1 month ago
1.10.2 Released Security release No LedgerSMB_Team Sat, 10/22/2022 - 12:31 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.10.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.10.2

* Fix multiple uploads through the [Attach] link failing (#6855)
* Fix '<< Return' link on the e-mail screen being broken in some cases (#6858)
* Improve query performance by declaring stored functions STABLE (#6872)
* Fix manual tax entry unavailable on saved invoices (#6791)
* Fix added line being dropped from invoice while deleting another (#6788)

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

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

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

Or pulled from the GitHub Container Registry
$ docker pull ghcr.io/ledgersmb/ledgersmb:1.10.2

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

These are the sha256 checksums of the uploaded files:

26f017cad0d74670f77f8ec04abd9b5b1fc203281e3cda4707d6f6d0c9012707 ledgersmb-1.10.2.tar.gz
03527966f5e99cf844fbb9d1f91481fd76143223b15df321590880344ea5eeb2 ledgersmb-1.10.2.tar.gz.asc

Release 1.10
LedgerSMB_Team

1.9.18 Released

1 month ago
1.9.18 Released Security release No LedgerSMB_Team Sat, 10/22/2022 - 12:30 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.9.18/

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

* Fix '<< Return' link on the e-mail screen being broken in some cases (#6858)
* Improve query performance by declaring stored functions STABLE (#6872)
* Fix added line being dropped from invoice while deleting another (#6788)

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

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

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

Or pulled from the GitHub Container Registry
$ docker pull ghcr.io/ledgersmb/ledgersmb:1.9.18

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

These are the sha256 checksums of the uploaded files:

3a21a696d8fb737001ddb10cb37050df625f697ed2d8a16f8dbd45dbce88e40f ledgersmb-1.9.18.tar.gz
a43b109bdf6accee6463748c994726718c358db6cef19fd7ab349fc7e93f5330 ledgersmb-1.9.18.tar.gz.asc

Release 1.9
LedgerSMB_Team

1.10.1 Released

1 month 2 weeks ago
1.10.1 Released Security release No LedgerSMB_Team Wed, 10/12/2022 - 10:40 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.10.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.10.1

* Fix batch details screen failing to load (#6850)
* Update 1.10.0 Perl dependency changes in Changelog
* Fix wrong taxes being applied to invoices (#6857)
* Fix HTML-encoding values on (PDF) printed documents (#6861)

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

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

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

Or pulled from the GitHub Container Registry
$ docker pull ghcr.io/ledgersmb/ledgersmb:1.10.1

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

These are the sha256 checksums of the uploaded files:

9a63258091e4409d0b4d37a1b32de59c0c839a2670593e8ce7ca6ed59001112d ledgersmb-1.10.1.tar.gz
57553c4bd47fcf0d8b74ef7fa40baac00c1b547c25646cfc93b018c31440592e ledgersmb-1.10.1.tar.gz.asc

Release 1.10
LedgerSMB_Team

1.9.17 Released

1 month 2 weeks ago
1.9.17 Released Security release No LedgerSMB_Team Wed, 10/12/2022 - 10:39 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.9.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.9.17

* Fix HTML-encoding values on (PDF) printed documents (#6861)
* Fix removal of invoice line breaking entire UI interaction (#6807)

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

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

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

Or pulled from the GitHub Container Registry
$ docker pull ghcr.io/ledgersmb/ledgersmb:1.9.17

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

These are the sha256 checksums of the uploaded files:

4a4fb6ad53ab88e20a0c35b55f547e60bcdcbc5792453b7bb9a308eb08017434 ledgersmb-1.9.17.tar.gz
57d1cec98be013dea93145d4ce7cd840d472447a75716e4c810809d0b477b319 ledgersmb-1.9.17.tar.gz.asc

Release 1.9
LedgerSMB_Team

Session expired immediately after logging in

1 month 2 weeks ago
Session expired immediately after logging in

When I log in, LedgerSMB 1.8 or higher immediately says my session has expired. What can I do to fix this?

ehu Mon, 10/10/2022 - 09:49

Short answer: add the "--preload-app" flag to the Starman command line.

Long answer: As of LedgerSMB 1.8, session information is stored in an encrypted cookie. To make sure the encryption key is unique for every installation, a new encryption secret is being generated each time LedgerSMB is started. However, Starman (without the "--preload-app" flag) loads the application in each forked worker separately, leading to different encryption secrets in each worker with the indicated behaviour as a result.

Component Base Release 1.8 1.9 1.10 FAQ Category Installation
ehu

1.10.0 Released

1 month 2 weeks ago
1.10.0 Released Security release No LedgerSMB_Team Sat, 10/08/2022 - 12:50 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.10.0/

The LedgerSMB development team is happy to announce the first release
of a new release branch: 1.10.0. This series features a wide variety
of new features, improvements, bug fixes and cleanup. To name a few:

* Ability to delete user login accounts (#1135)
* US/Washington tax module, doubling as an example for custom modules
* Possibility to add Vue component based pages
* User-modified workflows through "custom_workflows" config path setting
* Increased configurability by using dependency injection instead of configuration
* Default printer selection supports 'Screen' as default output location
* Default page size for PDFs selectable through System > Defaults
* Overpayment section in payment screen hidden on missing configuration (#2512)
* Batch AR/AP upload changed to support foreign currency transactions
* Some existing pages (including login.pl) converted to Vue.js v3
* INI-format configuration file replaced by YAML dependency injection file
* Localization of setup.pl & login.pl based on browser preferences
* Fixed: Tax incorrect on existing invoice after customer tax status change (#2322)
* Fixed: Full support for running from a schema other than 'public'
* Fixed: Printing checks fails to include invoices on the check's voucher (#6253)
* Start changing client to use Vue3, vue-router and vue-i18n
* Remove unused Dijit widget(s)
* Use more idiomatic Template Toolkit coding style for templates

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

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

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

Or pulled from the GitHub Container Registry
$ docker pull ghcr.io/ledgersmb/ledgersmb:1.10.0

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

These are the sha256 checksums of the uploaded files:

c10995dace3e4666759ec874cfa22ff3685214879c07e138e3644bded1e7e9b5 ledgersmb-1.10.0.tar.gz
c79711601c28e4bfdb7251f5b369d274260339a3aa53cea705757883f32fcbe6 ledgersmb-1.10.0.tar.gz.asc

Release 1.10
LedgerSMB_Team

Upgrade to LedgerSMB 1.10

1 month 2 weeks ago
Upgrade to LedgerSMB 1.10 Overview

Company database upgrades are supported all the way back from 1.4 directly to 1.10, using the 1.10 software. Company database upgrades from 1.3 and 1.2 are also supported, but due to the different nature of the upgrade process are called "migrations". The important difference being that when doing a migration, a copy of the data is being created in the 1.9 structure, while upgrades adjust the existing structure for 1.10. When upgrading from versions earlier than 1.9, please read the release notes and upgrade instructions and release notes of all the intermediate versions: these still apply but are not repeated here.

Before starting, please remember:

  • Create a backup
  • Don't do this when you're in a hurry
  • When running into problems, check out the "Support" page
Technical upgrade

Upgrading the software works the same as with prior versions. Please refer to the procedure to upgrade a tarball installation for 1.7 for the 1.10 upgrade. Be sure to install the new and updated Perl module dependencies listed in the Changelog. Also note that the Docker image definition contains a comprehensive list of Debian Bullseye package dependencies.

Especially note that the minimum versions for Perl and PostgreSQL have been updated. The minimum required Perl version is now 5.32 and the minimum required PostgreSQL version is now 13. (If you run Docker images, the Perl dependency is taken care of for you. The PostgreSQL dependency needs your attention.)

Prior versions of LedgerSMB run fine against PostgreSQL 13, so there is no reason to combine the 1.10 upgrade with the upgrade of PostgreSQL: you could upgrade to PostgreSQL 13 before upgrading LedgerSMB to 1.10.

Docker Compose upgrade

The docker compose infrastructure for all versions prior to 1.9 all used PostgreSQL 9.6; 1.9 required PostgreSQL 11. Unfortunately, the docker container does not upgrade the database itself -- meaning you'll need to export your PostgreSQL databases using pg_dumpall and restore it into the new database using psql as per the example.

(More comprehensive upgrade instructions are solicited; i.e. "help wanted".)

Company database upgrade

Technically, this process hasn't changed since 1.7 and the instructions for 1.7 still apply.

Each new LedgerSMB release has tightened the checks on validity of the data stored in the database. 1.10 continues on that path and adds yet more checks - this helps us find bugs and prevents undesirable data entering into the ledger. During the upgrade, existing data is checked against these new quality criteria and optionally offered for correction (or deletion, depending on the type of inconsistency).

Before you begin
  • Verify that all Reconciliation Reports have been either approved or deleted
    If you forget this step, the migration will offer to delete it for you; approval isn't supported during migration. Note that this does not refer to transactions; unapproved transactions can safely exist during upgrade.
  • Create a backup
  • Tell users not to use your system during upgrade
After the upgrade

    ehu Sat, 10/08/2022 - 09:59 Topic Installation Upgrade Release 1.10
    ehu

    Installing LedgerSMB 1.10

    1 month 2 weeks ago
    Installing LedgerSMB 1.10 Installation from tarballs

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

    System requirements

    Requirements for both clients and server are documented on the system requirements page.

    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.10.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 are assumed to be available. Running "dnf install perl-core" or "yum install perl-core" ensures the perl distribution is complete.

    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 of how to do that for Debian or Ubuntu.

    # 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 a 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

    For maximum security, it's important to go through the steps in this section: it allows you to run your setup with an administrator user which doesn't have superuser rights. Superuser accounts have rights to override access controls throughout PostgreSQL; the account created in this section won't. If you want to skip this section, please add a password to the "postgres" user using the command:

    # su - postgres -c "psql -c \"alter user postgres password 'YOURSECRET' valid until 'tomorrow'\""

    To create the more secure 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

    If you have decided not to create a dedicated database administrator account. Please make sure that your pg_hba.conf contains these two lines:

    host    all             all             127.0.0.1/32            scram-sha-256
    host    all             all             ::1/128                 scram-sha-256

    instead of the last two lines above which end in "peer". The remainder of this section isn't relevant if you're going to stick with the "postgres" superuser.

    If you decided to create a dedicated database administrator, please follow the remaining steps below.

    The 4 quoted lines above 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     scram-sha-256
    host    postgres,template0,template1   lsmb_dbadmin         ::1/128      scram-sha-256
    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     scram-sha-256
    host    all             all             ::1/128          scram-sha-256

    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.
    4. If you have an older Pg version, "scram-sha-256" may not be supported and needs to be replaced with "md5"

    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.6.3 <--- this line indicates success("9.6.3" 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 doc/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#" doc/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 doc/conf/ledgersmb.conf.default. Without configuration file, LedgerSMB runs with sensible default settings. If you want to change the defaults, install the configuration file with:

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

    And edit configuration to taste.

    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 Sat, 10/08/2022 - 01:43 Topic Installation Release 1.10
    ehu

    Preparing LedgerSMB 1.10 for first use

    2 months ago
    Preparing LedgerSMB 1.10 for first use

      This page explains how to set up LedgerSMB's first company after having completed installation, e.g. through the docker-compose.yml file. Please note that your full URL may differ depending on your installation method.

    In case you just completed the quick-start instructions, the base URL at which LedgerSMB is accessible is http://localhost:5762 (If you have a full production setup, you shouldn't need the port indicator [the ":5762" part]). There are two URLs (entry-points) you can use to access the application:

    • /setup.pl [full URL: http://localhost:5762/setup.pl ]
    • /login.pl [full URL: http://localhost:5762/login.pl ]

    The two entry points each serve their own purpose: setup.pl is the main tool for the database admin (lsmb_dbadmin); it serves to create new companies, create copies of companies, add users to companies and reset user's passwords. login.pl provides access to all other types of users.

    Creating the first company

    After browsing to setup.pl, the browser should show:

    In case the screen only shows the "Database" field, this indicates problems with JavaScript not having loaded correctly. Fill out the fields as follows:

    • Super-user login: lsmb_dbadmin
    • Password:
    • Database: testcompany

    Confirm the screen by clicking "Create". When the server is done creating the database for the company, a new screen will be returned. This can take up to 20 seconds.

    The resulting screen shows:

    Click "Skip" in order to skip loading a pre-defined Chart of Accounts. Select a country code and click Next to list the pre-defined charts of accounts.

    The resulting screen then shows a list of available Charts of Accounts:

    The screen above isn't shown when "Skip" was selected in the step before. Clicking "Skip" in this screen skips loading a pre-defined chart of accounts.

    Regardless of whether CoA loading was skipped or performed, the following screen will be presented:

    Select 'demo' templates for use with LaTeX. The exact choice made in this step is not highly important: templates can later be changed by loading new ones into the database. After confirming the selection by clicking "Load Templates", the following screen shows:

    With this screen, the first user for this company gets created. There are two modes:

    • Import (Yes): Assumes the username already exists in the database (e.g. because it is already used for another company; re-uses the existing username+password)
    • Create (No): Assumes the username does not already exist; will create a new username

    The "Assign Permissions" selection determines the rights assigned to the user:

    • "Full Permissions": The user may perform any task in the application
    • "Manage Users": The user has just enough rights to create new users who have appropriate rights

    For the purpose of this quick-start guide, enter the following details:

    • Username: first_user
    • Password: first_user
    • Import: No
    • Salutation: Mr
    • First Name: First
    • Last Name: User
    • Employee Number: 1
    • Date of Birth: (today's date)
    • Tax ID/SSN: 1
    • Country: (your country)
    • Assign Permissions: Full Permissions

    After confirming these data by clicking the "Create User" button, the following screen shows:

    First user login

    The "Start Using LedgerSMB" link opens the main application login screen, which can be used to log in using the initial user created above:

    Confirming login results in the following page*:

    Database administration of first company

    Once the testcompany has been created, it can be logged into through setup.pl as well as through login.pl. When logging in through setup.pl, the following screen with database administration functions shows:

    What's next?

    The system is now set up for evaluation and testing. The project has multiple channels to contact other users or the developers. Read all about that on the community project resources page.

    Any comments as to this specific article? Please sign up to the site and leave your comments below!

    ehu Sat, 09/24/2022 - 05:12 Release 1.10
    ehu

    1.10.0-beta3 Released

    2 months ago
    1.10.0-beta3 Released Security release No LedgerSMB_Team Sat, 09/24/2022 - 01:38 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.10.0-beta3/

    In preparation of the final release of LedgerSMB 1.10, the last preview version before final
    release was published earlier today: 1.10.0-beta3. Users are encouraged to download the Docker
    images or the tarball for evaluation purposes. Bugreports either in response to this mail or
    as GitHub issues are highly appreciated!

    For the list of major changes, please see the Changelog (https://github.com/ledgersmb/LedgerSMB/blob/master/Changelog#L6-L69).

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

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

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

    Or pulled from the GitHub Container Registry
    $ docker pull ghcr.io/ledgersmb/ledgersmb:1.10.0-beta3

    Or pulled from Docker Hub using the command
    $ docker pull ledgersmb/ledgersmb:1.10.0-beta3

    These are the sha256 checksums of the uploaded files:

    e52e3ca8aac22399c3ed98cf07b3e8bb946228e6d2145f57c6c3a7c2d555eb47 ledgersmb-1.10.0-beta3.tar.gz
    fb82764cb75b148eeb6d77a70033d3f873a9b0839bedbc04d49327a1061216af ledgersmb-1.10.0-beta3.tar.gz.asc

    Release 1.10
    LedgerSMB_Team

    1.9.16 Released

    3 months ago
    1.9.16 Released Security release No LedgerSMB_Team Wed, 08/24/2022 - 00:49 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.9.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.9.16

    * Support for PostgreSQL 14 for databases upgraded from pre-1.9.15

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

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

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

    Or pulled from the GitHub Container Registry
    $ docker pull ghcr.io/ledgersmb/ledgersmb:1.9.16

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

    These are the sha256 checksums of the uploaded files:

    775479093955fb8dcb26840ffd6feb8b67464c00333494054f3c347bf8b03b4a ledgersmb-1.9.16.tar.gz
    6947eacbbc8ca34ac309883d7d8ec6bdc8eb57b739863919f87a5f86a6a467ff ledgersmb-1.9.16.tar.gz.asc

    Release 1.9
    LedgerSMB_Team

    1.8.31 Released

    3 months ago
    1.8.31 Released Security release No LedgerSMB_Team Wed, 08/24/2022 - 00:48 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.8.31/

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

    * Support for PostgreSQL 14 for databases upgraded from pre-1.9.15

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

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

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

    Or pulled from the GitHub Container Registry
    $ docker pull ghcr.io/ledgersmb/ledgersmb:1.8.31

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

    These are the sha256 checksums of the uploaded files:

    7d0a0b7169b8e51094f3027f467639bb79f2ad949cc09b3125b662202433293b ledgersmb-1.8.31.tar.gz
    0b20c060baed1639171671238d197675af089d4f89f658aa643265361fb22459 ledgersmb-1.8.31.tar.gz.asc

    Release 1.8
    LedgerSMB_Team

    1.7.41 Released

    3 months ago
    1.7.41 Released Security release No LedgerSMB_Team Wed, 08/24/2022 - 00:48 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.41/

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

    * Support for PostgreSQL 14 for databases upgraded from pre-1.9.15

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

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

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

    Or pulled from the GitHub Container Registry
    $ docker pull ghcr.io/ledgersmb/ledgersmb:1.7.41

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

    These are the sha256 checksums of the uploaded files:

    8b69b9c16a20001248b8a46e48c6886bedcba73ce22999591a2fae54a83f6a6c ledgersmb-1.7.41.tar.gz
    9aea736ccbf0d20502e0f6080c747712c8b9460cd93d914a85cd8d7fbba0d859 ledgersmb-1.7.41.tar.gz.asc

    Release 1.7
    LedgerSMB_Team

    1.9.15 Released

    3 months 2 weeks ago
    1.9.15 Released Security release No LedgerSMB_Team Wed, 08/10/2022 - 13:49 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.9.15/

    The LedgerSMB development team is excited 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.9.15
    * Fix invoices randomly being incorrectly voided (#2321)
    * Fix response status code checks to correctly roll back on error (#6586)
    * Fix incorrect template delimiters in 'templates/demo/*.html' (#6659)

    Please note that this release fixes bug #2321 which the project
    team was never able to reproduce, but has been reported by
    different users many times over the past years.

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

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

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

    Or pulled from the GitHub Container Registry
    $ docker pull ghcr.io/ledgersmb/ledgersmb:1.9.15

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

    These are the sha256 checksums of the uploaded files:

    5346d6ee39537a7056aee1026ef3a03eade0882c3f5d7f7ff972a519408751a1 ledgersmb-1.9.15.tar.gz
    86bd23df7d3a5f66eaed2d798e594cf78370c571008c3cfdfdcc8488b8d0050a ledgersmb-1.9.15.tar.gz.asc

    Release 1.9
    LedgerSMB_Team

    1.8.30 Released

    3 months 2 weeks ago
    1.8.30 Released Security release No LedgerSMB_Team Wed, 08/10/2022 - 13:47 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.8.30/

    The LedgerSMB development team is excited 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.8.30

    * Fix invoices randomly being incorrectly voided (#2321)
    * Fix response status code checks to correctly roll back on error (#6586)

    Please note that this release fixes bug #2321 which the project
    team was never able to reproduce, but has been reported by
    different users many times over the past years.

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

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

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

    Or pulled from the GitHub Container Registry
    $ docker pull ghcr.io/ledgersmb/ledgersmb:1.8.30

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

    These are the sha256 checksums of the uploaded files:

    bac6b2374b744dbd8e67e4cda20428a8783b8c7d7fad6527e84539a3635b4888 ledgersmb-1.8.30.tar.gz
    c2d02a872c651ba6b503aae5997ed4d9972f0e6db35a68b3987645359f8c1eb9 ledgersmb-1.8.30.tar.gz.asc

    Release 1.8
    LedgerSMB_Team

    1.7.40 Released

    3 months 2 weeks ago
    1.7.40 Released Security release No LedgerSMB_Team Wed, 08/10/2022 - 13:46 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.40/

    The LedgerSMB development team is excited 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.40

    * Fix invoices randomly being incorrectly voided (#2321)
    * Reduce memory consumption rendering XLSX output (#6483)

    Please note that this release fixes bug #2321 which the project
    team was never able to reproduce, but has been reported by
    different users many times over the past years.

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

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

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

    Or pulled from the GitHub Container Registry
    $ docker pull ghcr.io/ledgersmb/ledgersmb:1.7.40

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

    These are the sha256 checksums of the uploaded files:

    e0eb994a0c8ff634c9e339ee6e9f45cbcde3e8186f700530be2565b4ed011bcf ledgersmb-1.7.40.tar.gz
    de0b274f60e071d9e7ddf0e4de3e719ed94f352bd7aaa2dc34ca3a0133bef246 ledgersmb-1.7.40.tar.gz.asc

    Release 1.7
    LedgerSMB_Team