Can I use the webservices using curl?

ehu — Sun, 13 Jun 2021 20:35:25 +0000

I'm writing this script in bash that I want to use to invoke functionality in LedgerSMB. Can I use curl and the webservices API to do that?

ehu Sun, 06/13/2021 - 13:35

Yes you can. In order to do so, you must first create a valid session for your follow-up requests by authenticating:

$ curl -c cookie-jar.txt -H 'Content-Type: application/json' \
    -d '{"login": "<your-user>", "password": "<your-password>", "company": "<your-company>"}' \
    https://example.org/login.pl?action=authenticate

The request above creates a file called "cookie-jar.txt" in the current directory which - after successful authentication - contains the authentication cookie to be used for follow-up requests. To use it, use curl's -b parameter:

$ curl -b cookie-jar.txt -c cookie-jar.txt -H 'Content-Type: application/json' \
    -d @request-body.json https://example.org/erp/api/v0/invoices/

Note that the use of curl's "-d" parameter implies that a POST request is issued. The presence of the at-sign in "@request-body.json" tells curl to read the request body from the file 'request-body.json'. When you decide not to use 'curl', but issue these requests from programming language, please make sure to issue POST requests.

OpenAPI documentation of the LedgerSMB API by version is available at https://docs.ledgersmb.org/openapi

Component

Base

Release

1.9

1.10

FAQ Category

Integration

Chat Support (Matrix)

Anonymous — Wed, 26 Dec 2012 19:21:35 +0000

Chat Support (Matrix)

For real-time help try our Matrix (IRC like) room #ledgersmb - you will usually find most of the core team hanging out there. The most feature-full and commonly used client is Element. It is available as a web client (for computers) and also as Android and iOS clients from within the appropriate app stores. We suggest you create a matrix account as that will allow you to log back in later to see our response to your question.

There are people there who range from users to developers who are willing to help. We have agreed to adopt the Ubuntu code of conduct for our community. Please read it if you plan on joining.

Please keep in mind that the community (especially the people you may need help from) are scattered around the world and will likely be in a different timezone to you. This means that it can sometimes take quite a few hours before someone responds. (although these days on IRC there is someone around almost all of the time). For email lists this is not a big problem, but if you are using Matrix (directly or via a matrix guest session) you will need to stay connected until someone answers otherwise we have no way to contact you :-)

If you ask for help as a signed up Matrix user, please log back in and check for a response occasionally, we will always respond as soon as someone is available.

NOTE: there is a nice feature of the Riot web app (a bell shaped icon near the top right) that shows all the messages that mention your name.
This is useful when you come back after a while to see if someone has responded to your question.
Just click on a message there to jump to that point in the chat history

Connecting to MATRIX

Read more about using Matrix and Element Client

Webclient

You can use a browser-based matrix client to join the channel.
It defaults to guest access with reduced features, but it is trivial to sign up and get additional benefits like channel history and other things.

Dedicated Chat client

Anonymous (not verified) Wed, 12/26/2012 - 11:21

Topic

Operating system

RedHat Enterprise Linux

Release

FAQ Category

1.11 release notes

ehu — Fri, 06 Jan 2023 21:35:30 +0000

1.11 release notes

Be sure to check the UPGRADE NOTES below!

What's new in LedgerSMB 1.11

New features

Feature 1

Description 1.

Note for upgrades: There is no impact on upgrades.

Webservices for GIFIs, SICs, Types of Business, Price groups, Warehouses and Languages

Webservices have been created to manage configuration of a number of entities:

Countries (/erp/api/v0/countries)

These were created in support of moving the front-end to Vue3 components, with the intent to use them as a learning experience for further API development. Due to this approach, the services do not support filtering, sorting or paging yet. For more information on how to use these services, see LedgerSMB Webservices.

Note for upgrades: There is no impact on upgrades.

Notable changes

Change summary 1

Explanation 1.

Note for upgrades: There are no consequences for upgrades: template sets used with 1.9 can be carried over without modification.

Upgrade notes

Sequences in System > Sequences switched to show "next value" instead of "last value"

If you use custom sequences, you need to increase the values in the Sequence column by 1 in order to prevent values from being used twice.

Background: The number shown in the "Sequence" column on the System > Sequences menu page, used to show the last value used. As of 1.11, it shows the next value that will be used. This ensures that value "1" in the sequence will be used now (it used to be skipped before), which helps auditability.

ehu Fri, 01/06/2023 - 13:35

Topic

Draft

Download

Anonymous — Sat, 01 Apr 2017 12:28:25 +0000

Download

Maintained releases

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

Official release distribution

The latest official release of LedgerSMB is always at download site. Releases are signed with GPG to assert integrity. Our public GPG key can be found on MIT's key server or on pgpkeys.eu. Install and upgrade info.

You can verify the release with the command

$ gpg --verify ledgersmb-<version>.tar.gz.asc ledgersmb-<version>.tar.gz

Docker images

There are production level Docker images available on GitHub. New containers are released on every stable (1.10) and old-stable (1.9) release. Docker images are around 250MB in size.

The docker repository identifier is "ledgersmb/ledgersmb" with the "latest" tag always pointing to the most recent stable release, which is currently the most recent 1.10.x release. The "master" tag points to the most recent alpha or beta of the development version (1.11).

Distribution packages

A Debian package is available in Debian v11 (stable, 'bullseye') and Debian v10 (oldstable, 'buster') but was not available in Debian v9 (Stretch, oldoldstable) due to problems with the Dojo dependency (which failed to build). Note that the current LedgerSMB version that is recommended for use is one in the 1.10.x series, which is not in Debian. We're working to get 1.8.x or 1.9.x packages into Debian.

Newer packages than those distributed by Debian can be found in the LedgerSMB APT repository (along with their updated dependancies as necessary).

Ubuntu packages are available in the standard distributions based off of the Debian packages.

Newer packages than those distributed in Ubuntu can be found in the LedgerSMB PPA repository.

RPM Packaging contributions solicited.

FreeBSD Packaging contributions solicited

OpenBSD Packaging contributions solicited.

Virtual Box No up-to-date images at this time.

Keeping up with the latest developments

The latest 1.9.x and 1.10.x are available directly from GitHub as a .zip file (it's not an official release, but has the latest fixes you may need) 1.9.x from GitHub, 1.10.x from GitHub. Check the repository for the change log in 1.10.x from GitHub or the changes in bleeding edge ('master').

LedgerSMB public GPG key
The LedgerSMB GPG public key can be found on the MIT key server. Here is the direct link.

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

Topic

Operating system

RedHat Enterprise Linux

Community overview 2022

ehu — Tue, 27 Dec 2022 16:59:22 +0000

Community overview 2022

As the year-end approaches, it's time to provide an overview of what
our community has achieved over the past year. At the end of last
year, I wished everybody a healthy and prosperous 2022 and now
is a time to look back and see how we did.

== Community interest ==

After years of decline in the number of hits on our website, this year
has broken the trend: ca 2,000 hits more than in 2021!
Traffic on the mailing lists was - in line with 2021 and 2020 - very low this
year. However, from the fact that during the year, we've seen the continued
increase in number of Stars and Forks on GitHub (Stars went up from 261
on 16 January 2022 to 304 today), we can conclude that there is still
interest in the project. Fortunately, with Covid behind us, new members
are coming to the project's chat channel on Element: people have time
to show their interest and contribute again.

== Releases ==

With the release of 1.10.0 on 08 October 2022, we realized our goal
to release 1.10 in the second half of the year, roughly a year after
1.9. With releases in the third quarter, we aim to provide mature software
before year-end -- when most companies close their books.
Despite the short release cycle, we were able to include a sizeable
list of new functionalities, changes and (code) cleanups through 1157
commits, 738 files changed, 236,716 added lines and 148,116 removed
lines of code (and comments) between 1.9.0 and 1.10.0.

With 37 releases across 4 maintenance branches in 2022, the project was
able to maintain the pace set in 2021 (which had 38 releases):

1.7 (4): 1.7.38 - 1.7.41
1.8 (15): 1.8.25 - 1.8.31
1.9 (6): 1.9.6 - 1.9.22
1.10 (9): 1.10.0 - 1.10.8

Which excludes the alpha, beta and release candidate releases.

== Packaging and installation ==

For 1.10, configuration has switched from the traditional "INI" file
configuration to enable/disable predefined options to a YAML based
configuration file declaring dependency injection. This switch was
made to support much more flexible customization options: entirely
new functionalities can now be added just through the configuration
file, instead of strictly en-/disabling existing ones.

== Development progress ==

This year saw similar numbers of commits as last year. Although the
number of commits was in the same range, the number of pull
requests (623) is lower than last year (827). The number of
active developers - derived from accepted commits - went back
down from 9 last year to 7 this year - the same as in 2020.

This year, too, we were able to close a number of long-standing
bugs/issues, continuing last year's focus to close as many issues
as possible in the 7-year-and-older range:

#1133: Add listing of user login accounts and employees
#1821: Allow page size for documents to be set through System > Defaults
#1881: Improve user feedback on saving, posting, etc of documents
#2321: VOID transaction does not reverse actual invoice

All from 2016 and 2015, just to name a few.

Project commits on all branches (excluding merges):
    927 Erik Huelsmann*
    132 Yves Lavoie*
     10 Aung Zaw Win*
      6 Neil Tiffin*
      5 Jeff Shelley*
      3 Hugh Esco
      2 Chris Travers

By comparison, these are the figures for 2021:
    895 Erik Huelsmann*
    139 Yves Lavoie*
     61 Aung Zaw Win*
     11 Neil Tiffin*
      4 Richard T. Weeks
      3 NoGare
      2 lianto.ruyang
      2 daOrangePeeler
      1 Xin Wang

Please note that the number of commits is in no way a measure of time
spent on the project. Also note that these numbers don't include the
time spent by those taking the effort to report their problems and
taking the time to respond to developer questions as well as helping
to test solutions when developers think they solved the problem.
Similarly, there was a lot of activity with respect to issues:

Number of open issues at 2022-01-01: 158
of which remain open today: 124

Issues closed: 92
of which created before 2022-01-01: 34

Issues created: 82
of which still open: 24

Number of open issues today: 148

This amount of development activity triggers many CI/CD jobs. To run
our test workloads, we have been using GitHub Actions as well as
CircleCI, each set up to test different aspects.

There isn't much in the 1.11 Changelog that we've spent time on that wasn't
included in a 1.10 maintenance release. Areas that we're
currently spending time on, include:

Driving the buttons on the AR/AP/Order screens from workflow configuration
Cleaning the code base from long-deprecated coding patterns such as DBObject
Creating more web services to drive migration of the front-end to Vue

The 148 issues that are open today summarize into these statistics:

8 bite-sized: a good place to start when looking to make contributions
51 enhancement: requesting new features added to the application
5 help wanted: looking for someone to help out on this issue
10 migration: these issues need help testing and developing migration from SQL Ledger
6 needs-documentation: there's not enough documentation...

(Note that an issue may fall into more than one category or none at all.)

== New functionality and improvements ==

Not an immediate feature by itself, but with 1.10 a lot of flexibility
was added through configuration by dependency injection. One of
the possibilities that have been unlocked with this change, is to have
PDF output based on other input formats than LaTeX (e.g. HTML).
The dependency injection change offers further improvements towards
increased flexibility by allowing different authentication mechanisms
and multiple workflow sources to be registered. All this to increase
possibilities for customization of installations.

== Looking forward to 2023 ==

In 2023, we'll likely release 1.11 around the third quarter;
again in a release cycle a bit shorter than a year. This year the
1.9 release branches will reach End-Of-Life status on 24 September
2023, as we have reverted back to only two concurrently supported
maintenance releases with a supported lifecycle of 2 years, meaning
that each year one will reach End-Of-Life.

And last but not least, I'm hoping for 1 or 2 new contributors (not
necessarily developers; translators, testers, documentation writers or
UI artists are all greatly appreciated!). If you want to contribute,
but don't know where to start, please contact me.

== In closing ==

Thanks to everybody who contributed to any of the above in any way,
especially to

Computerisms.ca for hosting our DNS
Freelock.com for hosting our website and mailing lists
Efficito.com for hosting our mailing list archive, apt repository,
release and download server
GitHub.com, CircleCI and coveralls.io for hosting our development workflow

My special personal thanks go to my GitHub Sponsors for supporting me
for time, efforts and (financial) resources dedicated to the project!

Leaves me only to wish everybody in our community - and their loved
ones - happy holidays and a safe and productive 2023!

ehu Tue, 12/27/2022 - 08:59

Installing LedgerSMB 1.10

ehu — Sat, 08 Oct 2022 08:43:06 +0000

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=<feature-name>" 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.
`starman`	Starman Perl/PSGI (standalone) web server
`openoffice`	OpenOffice.org document output
xls	Microsoft Excel XLS and XLSX 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:

A database administrator user (in PostgreSQL called a 'role') for creation and administration of LedgerSMB company databases
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/<version>/<cluster>/pg_hba.conf
RedHat derivatives: /var/lib/pgsql/<version>/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:

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

Open Source ERP: accounting, invoicing and more

Chris Travers — Sun, 18 Mar 2007 06:08:41 +0000

Open Source ERP: accounting, invoicing and more

Mission

The LedgerSMB project provides small and mid-size businesses with open source accounting software: integrating invoicing, order processing, quotations and more (ERP). LedgerSMB aims to provide a strong (multi-currency accounting) basis to build your business on -- without vendor lock-in.

Features

Sales (Invoices, Orders, Quotations)
Receivables & Payables
General ledger
Inventory management
Fixed asset accounting & depreciation
Profit & cost centers, departments, projects
Output documents in PDF, HTML, CSV, Office formats
Mail documents (e.g. invoices) from within the application
Translatable to your language (comes with 45 languages)
and more

The fact that LedgerSMB is open source - meaning that the source code is freely available - makes it even more customizable and flexible.

Use-cases

By industry

While LedgerSMB will generally work in any industry for its basic accounting functionalities, it is known to have been deployed in the following types of businesses:

Communications
e.g. VOIP services
Factoring
i.e. invoicing of others
(IT) Services
e.g. Website design, IT Support, hourly services
Financial services
e.g. Investment firms
Rental
e.g. Housing rental, IT Hosting
Retail
e.g. Sewing necessities
Trade
e.g. Trading pet foods

Many of these applications include integration with domain-specific applications to perform specific business functions.

Next to the ones listed above, various manufacturing setups have been deployed, ranging from standard (batch based) mass production, to make-to-order one-time product configurations. The latter being supported by a custom developed product configuration plugin.

By country

Although the nature of open source projects makes it hard to know where our software is being used; however, the project is aware of installations in the US, Canada, EU (Netherlands, Hungary, Estonia, United Kingdom), Indonesia, Myanmar, Philippines, Hong Kong, Malaysia, Australia, Barbados and Colombia.

The software can run in a different language for each user. Also: documents (invoices, orders, etc) can be produced in selectable languages, different from the user's language.

Contributions

The project welcomes any and all contributions. With lots of areas which would benefit from more attention, we like to invite newcomers to read our community guidelines and start out simple. Good (and helpful!) starting points are translation contributions as well as reviewing our (beginners) documentation.

Current versions

Our current stable version is 1.10 - initially released on Oct 8, 2022. This release has a wide variety of improvements and code cleanups: it features support for customized workflows, the ability to export document templates from the database, much more flexibility for customization by dependency injection, cleaned up document templates, login.pl & setup.pl being translated based on browser preferences and much more... More details about this release can be found in the release notes. This release will see its End-Of-Life for community support on Oct 8, 2024.

Our current stable version is 1.9 - initially released on Sep 24, 2021. This release has a wide variety of improvements and code cleanups: it features faster loading of pages, restored ability to mail aging reports regressed from 1.4, e-mailed documents (invoices, orders, etc) being stored in the database and much more... More details about this release can be found in the release notes. This release will see its End-Of-Life for community support on Sep 24, 2023.

Older versions

Version is 1.8 has been declared End-Of-Life on Sep 04, 2022 (released on Sep 04, 2020). This release has a wide variety of improvements and code cleanups: it features faster loading of the menu, fixed migrations from 1.2, the ability to upload a logo into the database and include it in printed documents and much more... More details about this release can be found in the release notes.

Version is 1.7 has been declared End-Of-Life on Oct 04, 2022 (released on Oct 04, 2019). This release focusses on improved support for foreign currency transactions, lifting the restriction of a single rate per currency per day; UI improved by showing both the functional and foreign currency amounts. Additionally, a lot of work has been spent on increasing the application stability through more rigorous testing and code cleanup. A full summary of the changes since 1.6 can be found in the release announcement. More details on this release can be found in the release notes.

Version 1.6 has been declared End-Of-Life on 2021, June 10th (released on June 10 2018). With 33 patch releases, we consider this version highly stable. Although there are more patch releases for 1.6 than thee are for 1.5, their size is on average smaller, attesting to the project's promise of delivering increasing software quality.

Version 1.5 has been declared End-Of-Life on 2019, Dec 23rd (released on 2016-12-23). With 30 patch releases, we consider this version highly stable. We believe that the lower number of patch releases over a similar life-span as 1.4 is an indication of better stability of the initial 1.5.0 release. We conclude that the project is delivering on its promise of increasing stability of minor releases.

Version 1.4 has been declared End-Of-Life on 2017, Sep 15th (released on 2014-09-15). With 42 patch releases, we consider this version highly stable.

Version 1.3 has been declared End-Of-Life on 2015, Dec 23rd (released on 2011-10-11). With a total of 48 patch releases since the initial release in October 2011, we consider this version highly stable.

Although their use is highly discouraged for both security reasons and data stability issues, older versions are still available for download. When using LedgerSMB versions 1.2 or earlier, you should to do so in only in a highly restricted network environment, because of known security problems.

It's project policy to provide at least 24 months of community support for every 1.x release series, aiming to have two versions supported at any time.

History

LedgerSMB began in 2006 as a fork of the popular general ledger software package called SQL-Ledger largely written and maintained by Dieter Simader since 1999. Versions 1.2 and earlier are heavily based on SQL-Ledger's code.
As of 1.3 our codebase is quickly moving away from what we inherited.
As of 1.5 our User Interface has moved to Dojo Javascript libraries providing a more dynamic feel.
Some of the improvements that we've made to the code base so far include:

Enhanced security
More reports
Better data integrity controls
More code quality control measures
Major code size reduction while growing functionality
Unit testing Infrastructure to help ensure once an issue is fixed it stays fixed
BDD (headless automated browser) Testing infrastructure
A very large number of tests against both testing frameworks

Travel in our history with Internet Archive and WayBackMachine.

Matrix support request ownership proof: ehuels@gmail.com

Chris Travers Sat, 03/17/2007 - 23:08

Controlling Starman

Anonymous — Sun, 27 Dec 2015 23:02:39 +0000

Controlling Starman

Useful Starman commands.
Using the perl based Starman webserver is the easiest way to run LedgerSMB locally (and quite possibly for production use as well).

Anonymous (not verified) Sun, 12/27/2015 - 15:02

## At the terminal, and from your LedgerSMB directory:
### Start Starman

starman  tools/starman.psgi

Default port is 5000.

starman -l :8080 tools/starman.psgi

Start with 8080 specified as the port.

Note: some documentation specifies the switch

--preload-app

It has been sugggested that this may give performance advantages in a production environment but isn't recommended while developing.
The manpage has more to say on this.

man starman

Based on that we currently would not recommend using --preload-app even on a production server

### While Starman is running

#### Reload Starman

pkill -HUP -f "starman master"

#### Restart Starman {#RestartStarman}

pkill -TERM -f "starman master"

#### Release the port if Starman is terminated
NOTE: try [Restart Starman](#RestartStarman) before doing this.

pkill -KILL -f "starman master"

Release

FAQ Category

Operating system

RedHat Enterprise Linux

Ubuntu

MacOS X

OpenBSD

Screenshots for 1.10

ehu — Mon, 31 Oct 2022 21:18:11 +0000

Screenshots for 1.10 ehu Mon, 10/31/2022 - 14:18

Topic

Screenshots

Release

1.10

How do I restore my data?

ehu — Mon, 13 May 2013 20:04:59 +0000

How do I restore my data? ehu Mon, 05/13/2013 - 13:04

Assuming you have followed the How Do I Backup My Data instructions, you can restore your database as follows...

Note LedgerSMB versions prior to version 1.9.16 did not support PostgreSQL 14 or higher due to a backward incompatible change in PostgreSQL 14.

Note that the following examples use the 'lsmb_dbadmin' for the database administrative user. Recent LedgerSMB installs do not automatically create an 'lsmb_dbadmin' user. This has to be created manually. You may have to use the 'postgres' user depending on how your database was installed.

1) Restore the roles

$ psql -h [database host] -U [database admin user] < [roles backup file]

For example:

$ psql -h localhost -U lsmb_dbadmin < lsmb-roles.sqlc

2) Create a new database to restore into

$ psql -h [database host] -U [database admin user] -c 'CREATE DATABASE [new company name]'

For example:

$ psql -h localhost -U lsmb_dbadmin -c 'CREATE DATABASE newcompany'

3) Restore the company backup into the new database:

$ psql -h [database host] -U [database admin user] [new company name] < [company backup file]

For example:

$ psql -h localhost -U lsmb_dbadmin newcompany < lsmb-db.sqlc

Release

FAQ Category

Topic

Recent content

Can I use the webservices using curl?

Chat Support (Matrix)

Connecting to MATRIX

Webclient

Dedicated Chat client

1.11 release notes

What's new in LedgerSMB 1.11

New features

Feature 1

Webservices for GIFIs, SICs, Types of Business, Price groups, Warehouses and Languages

Notable changes

Change summary 1

Upgrade notes

Sequences in System > Sequences switched to show "next value" instead of "last value"

Download

Maintained releases

Official release distribution

Docker images

Distribution packages

Keeping up with the latest developments

Community overview 2022

== Community interest ==

== Releases ==

== Packaging and installation ==

== Development progress ==

== New functionality and improvements ==

== Looking forward to 2023 ==

== In closing ==

Installing LedgerSMB 1.10

Installation from tarballs

Unpacking the release tarball

Next steps

Open Source ERP: accounting, invoicing and more

Mission

Features

Use-cases

By industry

By country

Contributions

Current versions

Older versions

History

Controlling Starman

Screenshots for 1.10

How do I restore my data?

1) Restore the roles

2) Create a new database to restore into

3) Restore the company backup into the new database: