LedgerSMB

Upgrading LedgerSMB 1.6.x to 1.6.y Upgrading tarball installations There are two steps to upgrading a LedgerSMB 1.6.x installation to 1.6.y (x smaller than y): Upgrade the software Upgrade the company database The last step has to ... [More] 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: Stop the LedgerSMB application server (e.g. Starman) $ sudo service starman-ledgersmb stop Back up the old software by moving it out of the way (assuming you installed in /usr/local/ledgersmb): $ sudo mv /usr/local/ledgersmb /usr/local/ledgersmb.backup Untar the tarball into /usr/local/ledgersmb: $ sudo tar xf ledgersmb-1.6.y.tar.gz --directory /usr/local Copy the configuration file from the old installation: $ sudo cp /usr/local/ledgersmb.backup/ledgersmb.conf /usr/local/ledgersmb/ Start the LedgerSMB application server again (Starman example given, as before): $ sudo service starman-ledgersmb start Upgrading the company database After the software has been upgraded, the company database(s) have to be upgraded. When a user logs in on a database which is of a version different from the software that's used to access the database, a "Database version mismatch" error will be generated. To upgrade the company database from the Web UI, navigate to the setup.pl page (e.g. when you're hosting your LedgerSMB on https://localhost/ and normally log in through https://localhost/login.pl, now you need to navigate to https://localhost/setup.pl). Log into setup.pl with the database admin credentials (the "lsmb_dbadmin" user, if you followed the installation instructions). After login, setup.pl will show a sccreen with the following at the top:   Logged in as lsmb_dbadmin LedgerSMB 1.6 db found Rebuild/Upgrade? By clicking the "Yes" button, the company database upgrade process will be executed. Repeat this process for all company databases. ehu Fri, 07/27/2018 - 08:19 Topic Upgrade Upgrading Installation Release 1.6 FAQ Category Administration [Less]

1.6.3 Released Security release No LedgerSMB_Team Sun, 07/22/2018 - 14:58 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.3/ ... [More] 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.6.3 Fix for menu System > Templates fails to execute SQL script (Erik H, #3588) Fix for GL journal buttons displaying in random order (Erik H, #3680) Fix for 'contact_all' role missing 'contact_vendor' rights (Erik H) Fix 1.6.1 regression browser failure to cache menu structure (Erik H) Erik H is Erik Huelsmann For installation instructions and system requirements, seehttps://github.com/ledgersmb/LedgerSMB/blob/1.6.3/README.md The release can be downloaded from our download site athttps://download.ledgersmb.org/f/Releases/1.6.3 The release can be downloaded from GitHub athttps://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.3 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.6.3 These are the sha256 checksums of the uploaded files: 5f23c7464dee8245f3a618f99526106ec79b8aa7608c3b7fb67408b13f9a13d9 ledgersmb-1.6.3.tar.gz db982d4e026caf3a71ddea2aa8811e7bb451e597c4afbcb33ce605b5cd09bcae ledgersmb-1.6.3.tar.gz.asc Release 1.6 [Less]

1.6.2 Released Security release No LedgerSMB_Team Sat, 06/23/2018 - 11:45 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.2/ ... [More] The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains fixes for two regressions in 1.6 over 1.5: Changelog for 1.6.2 Print button (to screen) doesn't work more than once (Erik H, #3705) Menu links ignore clicks long after first click (Erik H, #3704) Erik H is Erik Huelsmann For installation instructions and system requirements, seehttps://github.com/ledgersmb/LedgerSMB/blob/1.6.2/README.md The release can be downloaded from our download site athttps://download.ledgersmb.org/f/Releases/1.6.2 The release can be downloaded from GitHub athttps://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.2 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.6.2 These are the sha256 checksums of the uploaded files: e24c9f03d5fc306a10e0b759be7b65c44d75f47e19449cd6cefda83ff2d05c62 ledgersmb-1.6.2.tar.gz 60ec07555dc77a96eb590e1ae7792103021fc353ce98207468906926e0505018 ledgersmb-1.6.2.tar.gz.asc Release 1.6 [Less]

1.6.1 Released Security release No LedgerSMB_Team Sun, 06/17/2018 - 03:56 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.1/ ... [More] 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.6.1 Menu fails to show sometimes (Erik H, #3684) Error when managing user permissions through HR screen (Erik H, #3686) Reconciliation reports sometimes can't be submitted (Nick P) Erik H is Erik Huelsmann Nick P is Nick Prater For installation instructions and system requirements, seehttps://github.com/ledgersmb/LedgerSMB/blob/1.6.1/README.md The release can be downloaded from our download site athttps://download.ledgersmb.org/f/Releases/1.6.1 The release can be downloaded from GitHub athttps://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.1 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.6.1 These are the sha256 checksums of the uploaded files: badf997073eea49f8fd81a9db6c6d6ae7c91f13fa6f778d06677d9e9b00ffc18 ledgersmb-1.6.1.tar.gz d493654ec13433dec7ee6201c39b7dec4e9947d6afb8454369ba723954056d7c ledgersmb-1.6.1.tar.gz.asc Release 1.6 [Less]

1.6.0 Released Security release No ehu Sun, 06/10/2018 - 05:35 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.0 ... [More] The LedgerSMB development team is happy to announce the start of a new series of stable releases: 1.6.0. Over the past 18 months (since the release of 1.5.0) the team has worked on a multitude of aspects of the system with the primary focus to build a solid foundation for future development as well as reducing system complexity -- both at the code and installation levels. User Interface Reports and search results exportable to XLS(X) (Yves L) Left menu replaced by a (faster) Dojo-based version (Yves L/Erik H) Installation & Administration Added 'System Information' page to setup.pl for problem diagnosis (Erik H) Numerous improvements for the migrations and infrastructure (Yves L/Erik H) Better detection of incorrect @INC paths (David G) Automatic date format selection using browser locale (Yves L/Erik H) No more warnings from database creation and upgrade (Erik H) Improved logging: various logs correlated using unique request IDs (Erik H) Functions 'warn()' and 'die()' logged to debug logs (Erik H) Removed need for 'tempdir' and associated configuration option (Nick P) Removed numerous unused configuration options (Nick P) Specific output formats can be disabled in configuration (Yves L) Respect smtpuser and smtppass configuration options (Nick P) Add smtpport configuration option (Nick P) Database upgrades now ask for user input on (expected) faulty data (Erik H) Performance PSGI responses no longer written to file but kept in memory (Erik H/Yves L) Rewritten inventory tracking and adjustments Removed the need for the ill-understood 'Inventory Entity' (Erik H) Inventory adjustments GL transactions instead of dummy invoices (Erik H) SQL & in-browser(BDD) tests (Erik H) Code cleanup Removed code duplication in Template handling framework (Yves L) Remove unused variables and unreachable code (Nick P) Remove fragments of REST framework never fully implemented (Erik H) Authentication handling centralized in request dispatch code (Erik H) Cleaned up handling of uploaded files in request handling (Erik H) Moved to Plack::Request (from CGI::Simple & LedgerSMB) (Erik H) Template format plugin cleanup and refactoring (Erik H/Nick P) Template handling code cleanup (Erik H/Nick P) Unreferenced UI templates deleted (Erik H) Centralized and more robust entry point for code in old/ (Erik H) Merge of SQL-Ledger 2.8 and 3.0 migration code; improved consistency (Yves L) Improved cleanup of temp files and dirs after use (Erik H) Improved HTML structure (balanced closing/opening tags, etc) (Yves L) Factored HTTP response responsibility out of LedgerSMB::Template (Erik H) Moved request pre- and post-processing into custom Plack Middlewares (Erik H) Quality assurance Port testing of database routines to pgTAP (and Perl's 'prove') (Yves L) Enforce numerous Perl::Critic policies with code cleanup (Nick P/Rob R) Add tests for all template output formats (Nick P) Constrain password_duration setting to valid values (Nick P) Erik H is Erik Huelsmann Yves L is Yves Lavoie Nick P is Nick Prater Rob R is Rob Ransbottom David G is David Godfrey For installation instructions and system requirements, seehttps://github.com/ledgersmb/LedgerSMB/blob/1.6.0/README.md The release can be downloaded from our download site athttps://download.ledgersmb.org/f/Releases/1.6.0 The release can be downloaded from GitHub athttps://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.0 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.6.0 These are the sha256 checksums of the uploaded files: 97de4d0749b0789bf2f1e4fac1fa91e5fe936cd0889697b225f94b5255491484 ledgersmb-1.6.0.tar.gz 1a619c49b6c8a225c25bff74c4101a3d0ef988e37a8d0b7b2152784102419793 ledgersmb-1.6.0.tar.gz.asc Release 1.6 [Less]

1.5.21 Released Security release No ehu Sat, 06/02/2018 - 07:30 Release candidate No The LedgerSMB development team is happy to announce yet another new version of its ... [More] open source ERP and accounting application. This release contains the following fixes and improvements: Changelog for 1.5.21 * Clarify message after changing password through Preferences (Nick P) * Fix errors in ODS report tepmlate's title page (Nick P) * Fix #3642: Taxform report generation failing (Erik H) * Detect BOM to determine UTF-8 CSV imports (Erik H) Nick P is Nick Prater Erik H is Erik Huelsmann For installation instructions and system requirements, seehttps://github.com/ledgersmb/LedgerSMB/blob/1.5.21/README.md The release can be downloaded from our download site athttps://download.ledgersmb.org/f/Releases/1.5.21 The release can be downloaded from GitHub athttps://github.com/ledgersmb/LedgerSMB/releases/tag/1.5.21 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.5.21 These are the sha256 checksums of the uploaded files: 0262e77b9651521eca30bc69621dcdb68e7d13667facdaf845ad9bab23efc79e ledgersmb-1.5.21.tar.gz 1d1d2c858b46c22f0c29f201b42732a9d3b60c81f7bd0340c22031674b228683 ledgersmb-1.5.21.tar.gz.asc Release 1.5 [Less]

Installing LedgerSMB 1.6 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 ... [More] 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. Please note that installation of version 1.5 and up is completely different from the installation of versions 1.4 or earlier: This version uses Plack to handle integration with front-end web servers. This means LedgerSMB can now be run in combination with many web servers, including (but not limited to): nginx Starman lighttpd Apache It's no longer possible to run LedgerSMB as set of CGI scripts. This should not be a big concern, since Plack allows plugging LedgerSMB into Apache using mod_fcgid, mod_fastcgi or mod_proxy all of which have been available for versions 2.0 and up. Feel free to log in and share your experiences in the comments at the end of the article. System requirements Requirements are documented on the system requirements page. Client There are no specific requirements for LedgerSMB clients (web browsers) other than that they should have JavaScript enabled and be able to run Dojo 1.13. A broad range of browsers is supported (Chrome, FireFox, Opera, ...), including Microsoft Internet Explorer (10 or newer) and Microsoft Edge. Browsers explicitly not supported are: Lynx w3m IE9 or earlier 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.5.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 should be available. 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. # 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= These features are supported: Feature Description latex-pdf-ps Enable PDF and PostScript outputNote: 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 ehu Sat, 05/26/2018 - 05:33 Topic Installation Release 1.6 [Less]

Installing LedgerSMB 1.6 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 ... [More] 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. Please note that installation of version 1.5 and up is completely different from the installation of versions 1.4 or earlier: This version uses Plack to handle integration with front-end web servers. This means LedgerSMB can now be run in combination with many web servers, including (but not limited to): nginx Starman lighttpd Apache It's no longer possible to run LedgerSMB as set of CGI scripts. This should not be a big concern, since Plack allows plugging LedgerSMB into Apache using mod_fcgid, mod_fastcgi or mod_proxy all of which have been available for versions 2.0 and up. Feel free to log in and share your experiences in the comments at the end of the article.   System requirements Requirements are documented on the system requirements page. Client There are no specific requirements for LedgerSMB clients (web browsers) other than that they should have JavaScript enabled and be able to run Dojo 1.13. A broad range of browsers is supported (Chrome, FireFox, Opera, ...), including Microsoft Internet Explorer (10 or newer) and Microsoft Edge. Browsers explicitly not supported are: Lynx w3m IE9 or earlier 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.5.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 should be available. 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. # 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= These features are supported: Feature Description latex-pdf-ps Enable PDF and PostScript outputNote: 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 rest (EXPERIMENTAL) RESTful web services In order to install the starman and pdf/postscript output, the command becomes: # 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 an 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 The 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/ RedHat derivatives: /var/lib/pgsql/ 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 These lines 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     md5 host    postgres,template0,template1   lsmb_dbadmin         ::1/128      md5 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     md5 host    all             all             ::1/128          md5 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. 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- 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.4.7 $ 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 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#" 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) The reverse proxies documented below all have been and continuously are being tested and reviewed for correctly handling various kinds of malicious network traffic. 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: WORKING_DIR 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 conf/ledgersmb.conf.default. Install the configuration file with: # Install the default ledgersmb.conf configuration file $ cp conf/ledgersmb.conf.default ledgersmb.conf That is it. 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, 05/26/2018 - 05:33 Topic Installation Release 1.6 [Less]

Upgrade to LedgerSMB 1.6 (from 1.5 or 1.4/starman) Upgrading tarball installations There are two steps to upgrading a LedgerSMB 1.5.x to 1.6: Upgrade the software Upgrade the company database The last step must be executed for each ... [More] 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. Before upgrading, it is recommended to backup your databases. Note that all the steps below are prefixed with the 'sudo' command, but can be executed as 'root' directly as well. Upgrading the software These are the steps to follow, assuming an installation from tarball: Stop the LedgerSMB application server (e.g. Starman) $ sudo service starman-ledgersmb stop Back up the old software by moving it out of the way (assuming you installed in /usr/local/ledgersmb): $ sudo mv /usr/local/ledgersmb /usr/local/ledgersmb.backup Untar the tarball into /usr/local/ledgersmb: $ sudo tar xf ledgersmb-1.6.x.tar.gz --directory /usr/local Copy the configuration file from the old installation: $ sudo cp /usr/local/ledgersmb.backup/ledgersmb.conf /usr/local/ledgersmb/ Upgrade the LedgerSMB Starman SysV or systemd scripts (the new scripts can be found in /usr/local/ledgersmb/conf/systemd/ ) $ sudo cp /usr/local/ledgersmb/conf/systemd/ledgersmb_starman.service /etc/systemd/system/ledgersmb.service $ sudo systemctl daemon-reload Start the LedgerSMB application server again (Starman example given, as before): $ sudo service starman-ledgersmb start Upgrading the company database After the software has been upgraded, the company database(s) must be upgraded. Otherwise, when a user logs in on a database with a different version compared to the software, a "Database version mismatch" error will be generated. To upgrade the company database from the Web UI, navigate to the setup.pl page (e.g. when you're hosting your LedgerSMB on https://localhost/ and normally log in through https://localhost/login.pl, navigate to https://localhost/setup.pl). Log into setup.pl with the database admin credentials (the "lsmb_dbadmin" user, if you followed the installation instructions). After login, setup.pl will show a screen with the following at the top:   Logged in as lsmb_dbadmin LedgerSMB 1.5 db found Rebuild/Upgrade? By clicking the "Yes" button, the company database upgrade process will be executed. Repeat this process for all company databases. If upgrading from 1.4, rather than 1.5, note that the text will show "LedgerSMB 1.4 db found" instead. ehu Sat, 05/26/2018 - 03:19 Topic Installation Release 1.4 1.5 1.6 [Less]

1.6 release notes We're compiling a document here along the lines of http://subversion.apache.org/docs/release-notes/1.10.html What's new in LedgerSMB 1.6 Inventory adjustments based on GL transactions "System Information" page in ... [More] setup.pl New "smtpport" option in ledgersmb.conf Automatic detection of the temporary directory Reports and search results exportable as XLS(X) New and faster menu New features Inventory adjustments based on GL transactions Before 1.6, inventory adjustments were based on dummy invoices, issued to the "Inventory Entity" -- an entity meant to model the company itself. Issuing invoices for this purpose is problematic in some jurisdictions, especially in those with continuous numbering requirements. Additionally, the "Inventory entity" caused confusion for those who didn't need it. The Inventory Entity has been removed from 1.6 and - unless invoices remain issued against it after data migration - will be removed in the upgrade process. System Information page in setup.pl In the system administrator interface, there's a new "System Information" screen, which lists details of the system the application is running on, such as installed Perl modules, version of the PostgreSQL server and more. The data on this screen can be used for debugging purposes. It's highly encouraged to include (some) of the data on this page when reporting bugs to the project. New smtpport option in ledgersmb.conf Before 1.6, the SMTP port used for sending mail directly to a mail server, was hard-coded to be 25. Now, it's defaulted to port 25, but overridable from ledgersmb.conf. The SMTP host IP address always has been overridable; this option adds to that. Automatic detection of the temporary directory Before 1.6, the temporary directory would be indicated in ledgersmb.conf. As of 1.6, the Perl module File::Spec is being used to determine the temporary directory. In the past users were regularly experiencing problems with access rights to the self-created temporary directory managed by LedgerSMB. The process to create its own temporary directory has been removed as well, which takes away the source of the reports. Reports and search results exportable to XLS(X) With the correct dependencies installed, reports and search results can now be exported to XLS and XLSX formats in addition to the formats that were already there: PDF, HTML and CSV. New and faster menu   Other user-visible changes The need for the "Inventory Entity" used by the inventory adjustment process has been eliminated Known issues Single-day time-card entry is broken (since 1.4); weekly entry works though   ehu Thu, 05/03/2018 - 14:33 Topic release notes Release 1.6 [Less]