Recent content https://ledgersmb.org/index.php/ en Open Source ERP: accounting, invoicing and more https://ledgersmb.org/index.php/content/open-source-erp-accounting-invoicing-and-more <span class="field field--name-title field--type-string field--label-hidden">Open Source ERP: accounting, invoicing and more</span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><h1>Mission</h1> <p><a href="/statement-direction-ledgersmb">The LedgerSMB project</a> provides small and mid-size businesses with open source <a href="https://en.wikipedia.org/wiki/Accounting_software">accounting software</a>: integrating invoicing, order processing, quotations and more (<a href="https://en.wikipedia.org/wiki/Enterprise_resource_planning">ERP</a>). LedgerSMB aims to provide a strong (multi-currency accounting) basis to build your business on -- without vendor lock-in.</p> <h1><span style="line-height: 36.4000015258789px;">Features</span></h1> <ul><li>Sales (Invoices, Orders, Quotations)</li> <li>Receivables &amp; Payables</li> <li>General ledger</li> <li>Inventory management</li> <li>Fixed asset accounting &amp; depreciation</li> <li>Profit &amp; cost centers, departments, projects</li> <li>Output documents in PDF, HTML, CSV, Office formats</li> <li>Mail documents (e.g. invoices) from within the application</li> <li>Translatable to your language (comes with 45 languages)</li> <li><a href="http://ledgersmb.org/features">and more</a></li> </ul><p>The fact that LedgerSMB is <a href="https://opensource.org/osd">open source</a> - meaning that the source code is freely available - makes it even more customizable and flexible.</p> <h1 style="line-height: 36.4px;">Use-cases</h1> <h2>By industry</h2> <p>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:</p> <ul><li>Communications<br /> e.g. VOIP services</li> <li>Factoring<br /> i.e. invoicing of others</li> <li>(IT) Services<br /> e.g. Website design, IT Support, hourly services</li> <li>Financial services<br /> e.g. Investment firms</li> <li>Rental<br /> e.g. Housing rental, IT Hosting</li> <li>Retail<br /> e.g. Sewing necessities</li> <li>Trade<br /> e.g. Trading pet foods</li> </ul><p>Many of these applications include integration with domain-specific applications to perform specific business functions.</p> <p>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.</p> <h2>By country</h2> <p>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 <span class="mx_MTextBody mx_EventTile_content"><span class="mx_EventTile_body" dir="auto">US, Canada, EU (Netherlands, Hungary, Estonia, United Kingdom), Indonesia, Myanmar, Philippines, Hong Kong, Malaysia, Australia, Barbados and Colombia.</span></span></p> <p><span class="mx_MTextBody mx_EventTile_content"><span class="mx_EventTile_body" dir="auto">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.</span></span></p> <h1>Contributions</h1> <p>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 <a data-entity-substitution="canonical" data-entity-type="node" data-entity-uuid="c8075f26-dba4-48f6-bf53-3702c418dbdd" href="/index.php/content/community-guide" title="Community guide">community guidelines</a> and start out simple. Good (and helpful!) starting points are <a data-entity-substitution="canonical" data-entity-type="node" data-entity-uuid="3fc7f2b0-0844-4ae0-868b-90b968686d0f" href="/index.php/community-guide/community-guide/translating" title="Translating">translation contributions</a> as well as reviewing our (beginners) documentation.</p> <h1 style="line-height: 36.4px;">Current versions</h1> <p>Our current stable version is <a href="https://github.com/ledgersmb/LedgerSMB/tree/1.10"><em><strong>1.10</strong></em></a> - 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 &amp; setup.pl being translated based on browser preferences and much more... More details about this release can be found in the <a data-entity-substitution="canonical" data-entity-type="node" data-entity-uuid="fd6419af-309a-4ef9-9686-cfd876195cd0" href="/index.php/content/110-release-notes" title="1.10 release notes">release notes</a>. This release will see its End-Of-Life for community support on <strong>Oct 8, 2024</strong>.</p> <p>Our current stable version is <a href="https://github.com/ledgersmb/LedgerSMB/tree/1.9"><em><strong>1.9</strong></em></a> - 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 <a data-entity-substitution="canonical" data-entity-type="node" data-entity-uuid="59544c34-caac-4ca5-9a28-97b5b6a1c8f1" href="/index.php/content/19-release-notes" title="1.9 release notes">release notes</a>. This release will see its End-Of-Life for community support on <strong>Sep 24, 2023</strong>.</p> <h1>Older versions</h1> <p>Version is <a href="https://github.com/ledgersmb/LedgerSMB/tree/1.8"><em><strong>1.8</strong></em></a> 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 <a data-entity-substitution="canonical" data-entity-type="node" data-entity-uuid="ff891fb8-f65b-486c-a374-1510c5c24975" href="/index.php/content/18-release-notes" title="1.8 release notes">release notes</a>.</p> <p>Version is <em><a href="https://github.com/ledgersmb/LedgerSMB/tree/1.7"><strong>1.7</strong></a></em> 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 <a href="https://ledgersmb.org/content/17-release-notes">release notes</a>.</p> <p>Version <strong><em>1.6</em></strong> 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.</p> <p>Version <em><strong>1.5</strong></em> 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.</p> <p>Version <em><strong>1.4</strong></em> 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.</p> <p>Version <em><strong>1.3</strong></em> 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.</p> <p>Although their use is highly discouraged for both security reasons and data stability issues, older versions are still available for <a href="http://download.ledgersmb.org/f/Releases/">download</a>. 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.</p> <p>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.</p> <h1><a id="history" name="history"></a>History</h1> <p>LedgerSMB began in 2006 as a fork of the popular general ledger software package called <a class="ext" href="http://www.sql-ledger.com/" style="text-decoration: underline; ">SQL-Ledger</a> largely written and maintained by Dieter Simader since 1999. Versions 1.2 and earlier are heavily based on SQL-Ledger's code.<br /> As of 1.3 our codebase is quickly moving away from what we inherited.<br /> As of 1.5 our User Interface has moved to Dojo Javascript libraries providing a more dynamic feel.<br /> Some of the improvements that we've made to the code base so far include:</p> <ul><li>Enhanced security</li> <li>More reports</li> <li>Better data integrity controls</li> <li>More code quality control measures</li> <li>Major code size reduction while growing functionality</li> <li>Unit testing Infrastructure to help ensure once an issue is fixed it stays fixed</li> <li>BDD (headless automated browser) Testing infrastructure</li> <li>A very large number of tests against both testing frameworks</li> </ul><p>Travel in our history with Internet Archive and <a href="http://wayback.archive.org/web/*/http://www.ledgersmb.org">WayBackMachine</a>.</p> <p> </p> <p>Matrix support request ownership proof: ehuels@gmail.com</p> </div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>Chris Travers</span></span> <span class="field field--name-created field--type-created field--label-hidden">Sat, 03/17/2007 - 23:08</span> <section class="field field--name-comment-node-page field--type-comment field--label-hidden comment-wrapper"> </section> Sun, 18 Mar 2007 06:08:41 +0000 Chris Travers 153 at https://ledgersmb.org https://ledgersmb.org/index.php/content/open-source-erp-accounting-invoicing-and-more#comments Controlling Starman https://ledgersmb.org/index.php/faq/controlling-starman <span class="field field--name-title field--type-string field--label-hidden">Controlling Starman</span> <div class="clearfix text-formatted field field--name-field-detailed-question field--type-text-long field--label-hidden field__item"><p>Useful Starman commands.<br /> Using the perl based Starman webserver is the easiest way to run LedgerSMB locally (and quite possibly for production use as well).</p> </div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>Anonymous (not verified)</span></span> <span class="field field--name-created field--type-created field--label-hidden">Sun, 12/27/2015 - 15:02</span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>## At the terminal, and from your LedgerSMB directory:<br /> ### Start Starman</p> <pre>starman tools/starman.psgi</pre><p>Default port is 5000.</p> <pre>starman -l :8080 tools/starman.psgi</pre><p>Start with 8080 specified as the port.</p> <p>Note: some documentation specifies the switch</p> <pre>--preload-app</pre><p>It has been sugggested that this may give performance advantages in a production environment but isn't recommended while developing.<br /> The manpage has more to say on this.</p> <pre>man starman</pre><p>Based on that we currently would not recommend using --preload-app even on a production server</p> <p>### While Starman is running</p> <p>#### Reload Starman</p> <pre>pkill -HUP -f "starman master"</pre><p> #### Restart Starman {#RestartStarman}</p> <pre>pkill -TERM -f "starman master"</pre><p> #### Release the port if Starman is terminated<br /> NOTE: try [Restart Starman](#RestartStarman) before doing this.</p> <pre>pkill -KILL -f "starman master"</pre></div> <div class="field field--name-field-release field--type-entity-reference field--label-above"> <div class="field__label">Release</div> <div class="field__items"> <div class="field__item"><a href="/index.php/release/15" hreflang="en">1.5</a></div> </div> </div> <div class="field field--name-field-faq-category field--type-entity-reference field--label-above"> <div class="field__label">FAQ Category</div> <div class="field__item"><a href="/index.php/faq-categories/installation" hreflang="en">Installation</a></div> </div> <div class="field field--name-field-operating-system field--type-entity-reference field--label-above"> <div class="field__label">Operating system</div> <div class="field__items"> <div class="field__item"><a href="/index.php/operating-system/freebsd" hreflang="en">FreeBSD</a></div> <div class="field__item"><a href="/index.php/operating-system/linux" hreflang="en">Linux</a></div> <div class="field__item"><a href="/index.php/operating-system/centos" hreflang="en">CentOS</a></div> <div class="field__item"><a href="/index.php/operating-system/debian" hreflang="en">Debian</a></div> <div class="field__item"><a href="/index.php/operating-system/fedora" hreflang="en">Fedora</a></div> <div class="field__item"><a href="/index.php/operating-system/linux/gentoo" hreflang="en">Gentoo</a></div> <div class="field__item"><a href="/index.php/operating-system/redhat-enterprise-linux" hreflang="en">RedHat Enterprise Linux</a></div> <div class="field__item"><a href="/index.php/operating-system/linux/ubuntu" hreflang="en">Ubuntu</a></div> <div class="field__item"><a href="/index.php/operating-system/macos-x" hreflang="en">MacOS X</a></div> <div class="field__item"><a href="/index.php/operating-system/openbsd" hreflang="en">OpenBSD</a></div> </div> </div> <section class="field field--name-comment-node-faq field--type-comment field--label-hidden comment-wrapper"> </section> Sun, 27 Dec 2015 23:02:39 +0000 Anonymous 338 at https://ledgersmb.org https://ledgersmb.org/index.php/faq/controlling-starman#comments Screenshots for 1.10 https://ledgersmb.org/index.php/content/screenshots-110 <span class="field field--name-title field--type-string field--label-hidden">Screenshots for 1.10</span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>ehu</span></span> <span class="field field--name-created field--type-created field--label-hidden">Mon, 10/31/2022 - 14:18</span> <div class="field field--name-field-topic field--type-entity-reference field--label-above"> <div class="field__label">Topic</div> <div class="field__items"> <div class="field__item"><a href="/index.php/taxonomy/term/141" hreflang="en">Screenshots</a></div> </div> </div> <div class="field field--name-field-release field--type-entity-reference field--label-above"> <div class="field__label">Release</div> <div class="field__items"> <div class="field__item"><a href="/index.php/taxonomy/term/150" hreflang="en">1.10</a></div> </div> </div> <div class="field field--name-field-media field--type-entity-reference field--label-hidden field__items"> <div class="field__item"><article class="media media--type-screenshots media--view-mode-full"> <div class="field field--name-field-image field--type-image field--label-hidden field__item"> <a href="https://ledgersmb.org/sites/default/files/2022-10/f48e21d47d7d1544ed74faa1ef4ec3d3-step-post-1_0.png" aria-controls="colorbox" aria-label="{&quot;alt&quot;:&quot;1.10 Login screen&quot;}" role="button" title="1.10 Login screen" data-colorbox-gallery="gallery-all-7-SMPW4jSTk" class="colorbox" data-cbox-img-attrs="{&quot;alt&quot;:&quot;1.10 Login screen&quot;}"><img src="/sites/default/files/styles/max_325x325/public/2022-10/f48e21d47d7d1544ed74faa1ef4ec3d3-step-post-1_0.png?itok=fr_-UViJ" width="325" height="230" alt="1.10 Login screen" loading="lazy" class="image-style-max-325x325" /> </a> </div> </article> </div> <div class="field__item"><article class="media media--type-screenshots media--view-mode-full"> <div class="field field--name-field-image field--type-image field--label-hidden field__item"> <a href="https://ledgersmb.org/sites/default/files/2022-10/f48e21d47d7d1544ed74faa1ef4ec3d3-step-post-3.png" aria-controls="colorbox" aria-label="{&quot;alt&quot;:&quot;1.10 Admin interface login&quot;}" role="button" title="1.10 Admin interface login" data-colorbox-gallery="gallery-all-7-SMPW4jSTk" class="colorbox" data-cbox-img-attrs="{&quot;alt&quot;:&quot;1.10 Admin interface login&quot;}"><img src="/sites/default/files/styles/max_325x325/public/2022-10/f48e21d47d7d1544ed74faa1ef4ec3d3-step-post-3.png?itok=cKV7tffu" width="325" height="230" alt="1.10 Admin interface login" loading="lazy" class="image-style-max-325x325" /> </a> </div> </article> </div> <div class="field__item"><article class="media media--type-screenshots media--view-mode-full"> <div class="field field--name-field-image field--type-image field--label-hidden field__item"> <a href="https://ledgersmb.org/sites/default/files/2022-10/1e697f84931add8190179970614c7c8f-step-post-0.png" aria-controls="colorbox" aria-label="{&quot;alt&quot;:&quot;1.10 Welcome screen (after login)&quot;}" role="button" title="1.10 Welcome screen (after login)" data-colorbox-gallery="gallery-all-7-SMPW4jSTk" class="colorbox" data-cbox-img-attrs="{&quot;alt&quot;:&quot;1.10 Welcome screen (after login)&quot;}"><img src="/sites/default/files/styles/max_325x325/public/2022-10/1e697f84931add8190179970614c7c8f-step-post-0.png?itok=2T5hSzhO" width="325" height="230" alt="1.10 Welcome screen (after login)" loading="lazy" class="image-style-max-325x325" /> </a> </div> </article> </div> <div class="field__item"><article class="media media--type-screenshots media--view-mode-full"> <div class="field field--name-field-image field--type-image field--label-hidden field__item"> <a href="https://ledgersmb.org/sites/default/files/2022-10/1e697f84931add8190179970614c7c8f-step-post-4.png" aria-controls="colorbox" aria-label="{&quot;alt&quot;:&quot;1.10 Batch post (approval)&quot;}" role="button" title="1.10 Batch post (approval)" data-colorbox-gallery="gallery-all-7-SMPW4jSTk" class="colorbox" data-cbox-img-attrs="{&quot;alt&quot;:&quot;1.10 Batch post (approval)&quot;}"><img src="/sites/default/files/styles/max_325x325/public/2022-10/1e697f84931add8190179970614c7c8f-step-post-4.png?itok=ByxWEaE7" width="325" height="230" alt="1.10 Batch post (approval)" loading="lazy" class="image-style-max-325x325" /> </a> </div> </article> </div> <div class="field__item"><article class="media media--type-screenshots media--view-mode-full"> <div class="field field--name-field-image field--type-image field--label-hidden field__item"> <a href="https://ledgersmb.org/sites/default/files/2022-10/823cfa711d89778dd6e0d74b6d772f48-step-post-12.png" aria-controls="colorbox" aria-label="{&quot;alt&quot;:&quot;1.10 Bank Reconciliation&quot;}" role="button" title="1.10 Bank Reconciliation" data-colorbox-gallery="gallery-all-7-SMPW4jSTk" class="colorbox" data-cbox-img-attrs="{&quot;alt&quot;:&quot;1.10 Bank Reconciliation&quot;}"><img src="/sites/default/files/styles/max_325x325/public/2022-10/823cfa711d89778dd6e0d74b6d772f48-step-post-12.png?itok=vNGi-li1" width="325" height="230" alt="1.10 Bank Reconciliation" loading="lazy" class="image-style-max-325x325" /> </a> </div> </article> </div> <div class="field__item"><article class="media media--type-screenshots media--view-mode-full"> <div class="field field--name-field-image field--type-image field--label-hidden field__item"> <a href="https://ledgersmb.org/sites/default/files/2022-10/67b9ff63df723ffc820c4c63f77016f1-step-post-14.png" aria-controls="colorbox" aria-label="{&quot;alt&quot;:&quot;1.10 Balance sheet&quot;}" role="button" title="1.10 Balance sheet" data-colorbox-gallery="gallery-all-7-SMPW4jSTk" class="colorbox" data-cbox-img-attrs="{&quot;alt&quot;:&quot;1.10 Balance sheet&quot;}"><img src="/sites/default/files/styles/max_325x325/public/2022-10/67b9ff63df723ffc820c4c63f77016f1-step-post-14.png?itok=_Pmxi8qL" width="325" height="230" alt="1.10 Balance sheet" loading="lazy" class="image-style-max-325x325" /> </a> </div> </article> </div> <div class="field__item"><article class="media media--type-screenshots media--view-mode-full"> <div class="field field--name-field-image field--type-image field--label-hidden field__item"> <a href="https://ledgersmb.org/sites/default/files/2022-10/11054eefee3130c019ef7ce14a538d0c-step-post-26.png" aria-controls="colorbox" aria-label="{&quot;alt&quot;:&quot;1.10 AR transaction entry&quot;}" role="button" title="1.10 AR transaction entry" data-colorbox-gallery="gallery-all-7-SMPW4jSTk" class="colorbox" data-cbox-img-attrs="{&quot;alt&quot;:&quot;1.10 AR transaction entry&quot;}"><img src="/sites/default/files/styles/max_325x325/public/2022-10/11054eefee3130c019ef7ce14a538d0c-step-post-26.png?itok=jYyXiZKc" width="325" height="230" alt="1.10 AR transaction entry" loading="lazy" class="image-style-max-325x325" /> </a> </div> </article> </div> <div class="field__item"><article class="media media--type-screenshots media--view-mode-full"> <div class="field field--name-field-image field--type-image field--label-hidden field__item"> <a href="https://ledgersmb.org/sites/default/files/2022-10/11054eefee3130c019ef7ce14a538d0c-step-post-91.png" aria-controls="colorbox" aria-label="{&quot;alt&quot;:&quot;1.10 GL transaction entry&quot;}" role="button" title="1.10 GL transaction entry" data-colorbox-gallery="gallery-all-7-SMPW4jSTk" class="colorbox" data-cbox-img-attrs="{&quot;alt&quot;:&quot;1.10 GL transaction entry&quot;}"><img src="/sites/default/files/styles/max_325x325/public/2022-10/11054eefee3130c019ef7ce14a538d0c-step-post-91.png?itok=A4CFOR_h" width="325" height="230" alt="1.10 GL transaction entry" loading="lazy" class="image-style-max-325x325" /> </a> </div> </article> </div> </div> <section class="field field--name-comment-node-article field--type-comment field--label-hidden comment-wrapper"> </section> Mon, 31 Oct 2022 21:18:11 +0000 ehu 608 at https://ledgersmb.org https://ledgersmb.org/index.php/content/screenshots-110#comments How do I restore my data? https://ledgersmb.org/index.php/faq/how-do-i-restore-my-data <span class="field field--name-title field--type-string field--label-hidden">How do I restore my data?</span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>ehu</span></span> <span class="field field--name-created field--type-created field--label-hidden">Mon, 05/13/2013 - 13:04</span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>Assuming you have followed the <a href="/faq/how-do-i-backup-my-data">How Do I Backup My Data</a> instructions, you can restore your database as follows...</p> <p>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.</p> <p><strong>Note</strong> 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.</p> <h2>1) Restore the roles</h2> <pre> $ psql -h [database host] -U [database admin user] &lt; [roles backup file]</pre> <p>For example:</p> <pre> $ psql -h localhost -U lsmb_dbadmin &lt; lsmb-roles.sqlc</pre> <h2>2) Create a new database to restore into</h2> <pre> $ psql -h [database host] -U [database admin user] -c 'CREATE DATABASE [new company name]'</pre> <p>For example:</p> <pre> $ psql -h localhost -U lsmb_dbadmin -c 'CREATE DATABASE newcompany'</pre> <h2>3) Restore the company backup into the new database:</h2> <pre> $ psql -h [database host] -U [database admin user] [new company name] &lt; [company backup file]</pre> <p>For example:</p> <pre> $ psql -h localhost -U lsmb_dbadmin newcompany &lt; lsmb-db.sqlc </pre> </div> <div class="field field--name-field-release field--type-entity-reference field--label-above"> <div class="field__label">Release</div> <div class="field__items"> <div class="field__item"><a href="/index.php/release/all-versions" hreflang="en">All Versions</a></div> <div class="field__item"><a href="/index.php/release/10" hreflang="en">1.0</a></div> <div class="field__item"><a href="/index.php/release/11" hreflang="en">1.1</a></div> <div class="field__item"><a href="/index.php/release/12" hreflang="en">1.2</a></div> <div class="field__item"><a href="/index.php/release/13" hreflang="en">1.3</a></div> <div class="field__item"><a href="/index.php/release/14" hreflang="en">1.4</a></div> <div class="field__item"><a href="/index.php/release/15" hreflang="en">1.5</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/142" hreflang="en">1.6</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/146" hreflang="en">1.7</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/147" hreflang="en">1.8</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/149" hreflang="en">1.9</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/150" hreflang="en">1.10</a></div> <div class="field__item"><a href="/index.php/release/20" hreflang="en">2.0</a></div> </div> </div> <div class="field field--name-field-faq-category field--type-entity-reference field--label-above"> <div class="field__label">FAQ Category</div> <div class="field__item"><a href="/index.php/faq-categories/administration" hreflang="en">Administration</a></div> </div> <div class="field field--name-field-topic field--type-entity-reference field--label-above"> <div class="field__label">Topic</div> <div class="field__items"> <div class="field__item"><a href="/index.php/topics/backup" hreflang="en">Backup</a></div> <div class="field__item"><a href="/index.php/topics/restore" hreflang="en">Restore</a></div> </div> </div> <section class="field field--name-comment-node-faq field--type-comment field--label-hidden comment-wrapper"> </section> Mon, 13 May 2013 20:04:59 +0000 ehu 247 at https://ledgersmb.org https://ledgersmb.org/index.php/faq/how-do-i-restore-my-data#comments Which versions do you support? https://ledgersmb.org/index.php/faq/which-versions-do-you-support <span class="field field--name-title field--type-string field--label-hidden">Which versions do you support?</span> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>ehu</span></span> <span class="field field--name-created field--type-created field--label-hidden">Sun, 12/30/2012 - 03:17</span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><h1>Active support</h1> <p>Versions 1.9 and higher are under active development and are supported by the community. Planned end-of-life dates for current releases are:</p> <ul><li>1.9: Planned End-of-life date: 2023-09-24 (released 2021-09-24)</li> <li>1.10: Planned End-of-life date: 2024-10-08 (released 2022-10-08)</li> </ul><h1 style="line-height: 36px;">End of life</h1> <p>If you're looking for help on how to use EOL-ed versions, please try mailing <a href="https://lists.ledgersmb.org/mailman/listinfo/users">the users mailing</a> list.<br /> If you're looking for someone to create bugfixes, please check with one of the parties providing <a href="http://ledgersmb.org/topic/commercial-support">commercial support</a> or for less urgent fixes <a href="https://github.com/ledgersmb/LedgerSMB/issues">LedgerS</a><a href="https://github.com/ledgersmb/LedgerSMB/issues">MB Issues</a></p> <p>Version 1.8 has been declared end-of-life on 2022-09-04. The last release in the series is 1.8.31. No futher releases will be made by the community.</p> <p>Version 1.7 has been declared end-of-life on 2022-10-04. The last release in the series is 1.7.41. No further releases will be made by the community.</p> <p>Version 1.6 has been declared end-of-life on 2021-06-10. The last release in the series is 1.6.33. No further releases will be made by the community.</p> <p>Version 1.5 has been declared end-of-life on 2019-12-23. The last release in the series is 1.5.30. No further releases will be made by the community.</p> <p>Version 1.4 has been declared end-fo-life on 2017-09-16. The last release in the series is 1.4.42. No further releases will be made by the community.</p> <p>Version 1.3 has been declared end-of-life on 2015-12-23. The last release in the series is 1.3.47. No further releases will be made by the community.</p> <p>LedgerSMB versions 1.0, 1.1 and 1.2 won't be maintained any further due to the fact that there are some known security issues which can't be fixed.<!--break--></p> </div> <div class="field field--name-field-release field--type-entity-reference field--label-above"> <div class="field__label">Release</div> <div class="field__items"> <div class="field__item"><a href="/index.php/release/all-versions" hreflang="en">All Versions</a></div> <div class="field__item"><a href="/index.php/release/10" hreflang="en">1.0</a></div> <div class="field__item"><a href="/index.php/release/11" hreflang="en">1.1</a></div> <div class="field__item"><a href="/index.php/release/12" hreflang="en">1.2</a></div> <div class="field__item"><a href="/index.php/release/13" hreflang="en">1.3</a></div> <div class="field__item"><a href="/index.php/release/14" hreflang="en">1.4</a></div> <div class="field__item"><a href="/index.php/release/15" hreflang="en">1.5</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/142" hreflang="en">1.6</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/146" hreflang="en">1.7</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/147" hreflang="en">1.8</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/149" hreflang="en">1.9</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/150" hreflang="en">1.10</a></div> <div class="field__item"><a href="/index.php/release/20" hreflang="en">2.0</a></div> </div> </div> <div class="field field--name-field-faq-category field--type-entity-reference field--label-above"> <div class="field__label">FAQ Category</div> <div class="field__item"><a href="/index.php/faq-categories/support" hreflang="en">Support</a></div> </div> <div class="field field--name-field-topic field--type-entity-reference field--label-above"> <div class="field__label">Topic</div> <div class="field__items"> <div class="field__item"><a href="/index.php/topics/support" hreflang="en">Support</a></div> <div class="field__item"><a href="/index.php/topics/security" hreflang="en">Security</a></div> <div class="field__item"><a href="/index.php/topics/end-life" hreflang="en">End Of Life</a></div> </div> </div> <section class="field field--name-comment-node-faq field--type-comment field--label-hidden comment-wrapper"> </section> Sun, 30 Dec 2012 11:17:51 +0000 ehu 217 at https://ledgersmb.org https://ledgersmb.org/index.php/faq/which-versions-do-you-support#comments Commercial support https://ledgersmb.org/index.php/content/commercial-support <span class="field field--name-title field--type-string field--label-hidden">Commercial support</span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>Commercial support for LedgerSMB is also available. This can be installation support, training, custom features or hosting. Currently there are several commercial support providers:</p> <ul><li><a href="http://www.efficito.com"><span style="line-height: 1.5;">Efficito</span></a><br /> Efficito offers hosting, support, and customization for LedgerSMB.  Co-founders Chris Travers and Erik Huelsmann are both core contributors and committee members.</li> <li><a href="http://www.metatrontech.com/">Metatron Technology Consulting</a><br /> Chris Travers of Metatron Technology is a core LedgerSMB committee member and deeply involved in all aspects of the project</li> <li> <p><a href="http://MrKask.com">MrKask.com</a><br /> Maanus Kask as Mr Kask offers hosting, support, and customization for LedgerSMB in Estonia</p> </li> </ul></div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>Anonymous (not verified)</span></span> <span class="field field--name-created field--type-created field--label-hidden">Fri, 04/13/2007 - 18:14</span> <div class="field field--name-field-topic field--type-entity-reference field--label-above"> <div class="field__label">Topic</div> <div class="field__items"> <div class="field__item"><a href="/index.php/topics/support" hreflang="en">Support</a></div> </div> </div> <section class="field field--name-comment-node-article field--type-comment field--label-hidden comment-wrapper"> </section> Sat, 14 Apr 2007 01:14:09 +0000 Anonymous 21 at https://ledgersmb.org https://ledgersmb.org/index.php/content/commercial-support#comments 1.10 release notes https://ledgersmb.org/index.php/content/110-release-notes <span class="field field--name-title field--type-string field--label-hidden">1.10 release notes</span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><h1><span id="cke_bm_63S" style="display: none;"> </span>What's new in LedgerSMB 1.10</h1> <ul><li>Ability to delete user login accounts</li> <li>US/Washington tax module</li> <li>User-modified workflows</li> <li>Full support for running in a schema other than "public"</li> <li>Batch aging statements printing and mailing with language selection</li> <li>Webservices for GIFIs, SICs, Types of Business, Pricegroups, Warehouses and Languages</li> <li>Experimental webservice for invoices</li> <li>Default printer selection in user preferences</li> <li>Language names in drop-downs in the language of the user</li> </ul><p><!--break--></p> <h1>New features</h1> <h2>Ability to delete user login accounts</h2> <p>Starting the 1.10 release, it's possible to detach a login account from an employee. To do so, open the User screen through "HR &gt; Employees &gt; Search" and selecting the employee with the user to be removed.</p> <p>The effect of this action is that the database login account associated with this employee is removed, preventing any form of use either by the user or by admins.</p> <p><strong>Note for upgrades</strong>: There is no impact on upgrades.</p> <h2>US/Washington tax module</h2> <p>This release comes with an example of how to implement and configure a custom tax module in the directory "utils/wa-tax-service/". To perform its function, this module calls an external webservice to calculate its taxes. Based on the response, it sets both the taxes as well as a value in the "Source" field of the transaction table, for tracking purposes.</p> <p>Note that this example is fully functional and used in production, so if you are in US/WA, you may want to use this module.</p> <p><strong>Note for upgrades</strong>: There is no impact on upgrades.</p> <h2>User-modified workflows</h2> <p>Default workflow configurations are stored in "workflows/". Users are expected to change workflow definitions. To prevent changed workflow definitions from being overwritten on upgrade, customized workflows will be loaded from "custom_workflows/". Workflow files which have <em>not</em> been customized, will still be loaded from "workflows/".</p> <p><strong>Note for upgrades</strong>: There is no impact on upgrades.</p> <h2>Full support for running in a schema other than "public"</h2> <p>For a long time the example configuration file has suggested that LedgerSMB can run in a schema other than the default "public" schema by offering a "namespace" setting which was documented to declare the name of the schema in which the LedgerSMB tables are located. Support for this feature was far from complete. This release comes with the missing functionality. The continuous integration tests are now run in a schema other than "public", proving this functionality on each test run again.</p> <p><strong>Note for upgrades</strong>: There is no impact on upgrades.</p> <h2>Batch aging statement printing and mailing with language selection</h2> <p>Printing multiple aging statements has been fixed to support the language selector per statement, which it was lacking since late 1.3. Mailing multiple aging statements was broken similarly with respect to language selection. Additionally, it was broken in the sense that it would mail out only the first of the selected statements, returning the user to the statement selection screen.</p> <p>Printing multiple statements now returns  a ZIP archive with all the selected statements in the selected language for each statement. Mailing multiple statements leads to a series of e-mails being created with the statements as attachment, which can be edited and sent (individually). Further improvement is foreseen to allow for providing templated text to send the mails in batch.</p> <p><strong>Note for upgrades</strong>: There is no impact on upgrades.</p> <h2>Webservices for GIFIs, SICs, Types of Business, Price groups, Warehouses and Languages</h2> <p>Webservices have been created to manage configuration of a number of entities:</p> <ul><li>GIFI (/erp/api/v0/gl/gifis)</li> <li>SIC [standard industry code] (/erp/api/v0/contacts/sics)</li> <li>Type of Business (/erp/api/v0/contacts/business-types)</li> <li>Price group (/erp/api/v0/products/pricegroups)</li> <li>Warehouse (/erp/api/v0/products/warehouses)</li> <li>Language (/erp/api/v0/languages)</li> </ul><p>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  <a href="https://docs.ledgersmb.org/openapi" title="LedgerSMB Webservices">LedgerSMB Webservices</a>.</p> <p><strong>Note for upgrades</strong>: There is no impact on upgrades.</p> <h2>Experimental webservice for invoices</h2> <p>A webservice experiment has been created for posting (creating) invoices and retrieving (single) invoices: /erp/api/v0/invoices. The api is marked experimental, because it's likely to change in a later release (1.11 or later) when a more complete and REST compliant design will be implemented. There is currently no timeline for this. Changes to the invoice API will be announced through the release notes.</p> <p><strong>Note for upgrades</strong>: There is no impact on upgrades.</p> <h2>Default printer selection in user preferences</h2> <p>Starting with 1.10, it will be possible for users to select "Screen" as their default printer. This way, users can reliably have the Screen target selected with the possibility to deviate where desired.</p> <p>Additionally, the default printer selection in preferences page did not show. This has been fixed to support the "Screen" selection, meaning that for many users being able to select a default printer will be a new functionality.</p> <p><strong>Note for upgrades</strong>: There is no impact on upgrades.</p> <h2>Language names in drop-downs in the language of the user</h2> <p>The language selection drop-down would be populated with English names for the language name options, even when using a properly translated user interface. As of this release, translations for language names are derived from <a href="https://cldr.unicode.org/">the Unicode Common Locale Data Repository</a> to make for a more consistent experience.</p> <p><strong>Note for upgrades</strong>: There is no impact on upgrades.</p> <h1>Notable changes</h1> <h2>"xedemo" template set merged with "demo" set</h2> <p>There were minimal differences between the "demo" and "xedemo" template sets: all templates other than the *.tex templates were identical. The *.tex templates differed only by their use of "fontspec" versus "fontenc+inputenc" packages and some font selection instructions. These differences have now been catered for using the "iftex" package.</p> <p><strong>Note for upgrades</strong>: There are no consequences for upgrades: template sets used with 1.9 can be carried over without modification.</p> <h2>"setup.pl" and "login.pl" translated based on browser preferences</h2> <p>The setup.pl and login.pl pages detect the language preferences configured in the user's browser and - when available - use the requested language for translation, localization (date and number formats) and text orientation. Please note that users configure their own language, date and number formatting preferences in the user preference page which overrules the browser choice.</p> <p><strong>Note for upgrades</strong>: There are no special considerations for upgrades.</p> <h2>Templates for balance sheet and income statement cleaned</h2> <p>In various releases, PNL and balance sheet templates were distributed either broken for the hierarchical or the account-type report form. This release fixes both and cleans links from the HTML reports (that is, the reports that are downloaded).</p> <p><strong>Note for upgrades</strong>: To use the fixed templates, upload them into every company database you want to use them with.</p> <h2>Increased configurability through YAML with dependency injection</h2> <p>In addition to INI file based configuration, LedgerSMB now also supports much more extensive YAML based configuration. This change has been made to support more complex customization scenarios. One example of what this change means is being able how output documents are produced: until now, output PDF documents are hard-coded to be generated from LaTeX, but after this change, it has become possible to produce PDF from HTML by registering a custom output plugin which knows how to do that transformation.</p> <p><strong>Note for upgrades</strong>: People wanting to benefit from this increased flexibility should move their INI file configuration to YAML using the utils/migration/migrate-ini-to-di script, storing the result in ledgersmb.yaml and renaming the ini file to ledgersmb.ini-backup.</p> <h1>Upgrade notes</h1> <h2>AR Aging statement  template changed</h2> <p>The AR Aging statement template changed. Please upload the new template into your company database. The old template will render completely empty aging statements.</p> <p>This change is related to the changes in batch printing aging statements and the language selection drop-down.</p> <h2>AR/AP transaction print templates</h2> <p>In 1.10, the line item descriptions on AR/AP transaction print templates have been renamed from "description" to "linedescription" to eliminate overlapping use of the "description" field. This means you need to either re-import the templates (which can be done through "setup.pl") or change all occurrences of:</p> <pre> description.${lc}</pre> <p>and</p> <pre> description.${loop_count}</pre> <p>respectively to:</p> <pre> linedescription.${lc}</pre> <p>or</p> <pre> linedescription.${loop_count}</pre> <p>This applies to both AR and AP transaction templates (accessible through the System &gt; Templates menu), for all formats (csv, tex and html).</p> <h2>Template variables renamed</h2> <p>The in-database templates for (printed) documents, have changed. After upgrading, it is either necessary to re-import the templates, or, to adjust existing templates if they have been customized. The following variables have been renamed or removed:</p> <ul><li>"company_name" is now available under "SETTINGS.company_name"</li> <li>"company_address" is now available under "SETTINGS.company_address"</li> <li>"request.${HLINE.value}" is now available under "HLINE.value"</li> <li>"request.${LINE.value}" is now available under "LINE.value"</li> <li>Everything starting with "request." is no longer available</li> </ul><p>The values which are available under another name need to be replaced by their new names.</p> </div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>ehu</span></span> <span class="field field--name-created field--type-created field--label-hidden">Mon, 03/28/2022 - 13:29</span> <div class="field field--name-field-release field--type-entity-reference field--label-above"> <div class="field__label">Release</div> <div class="field__items"> <div class="field__item"><a href="/index.php/taxonomy/term/150" hreflang="en">1.10</a></div> </div> </div> <section class="field field--name-comment-node-article field--type-comment field--label-hidden comment-wrapper"> </section> Mon, 28 Mar 2022 20:29:49 +0000 ehu 583 at https://ledgersmb.org https://ledgersmb.org/index.php/content/110-release-notes#comments Roadmap https://ledgersmb.org/index.php/content/roadmap <span class="field field--name-title field--type-string field--label-hidden">Roadmap</span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>This document looks forward from the last stable public release (currently 1.6). The document should be taken as a general indication of direction. As with every open source project, contributors follow their own priorities; as such, features may be implemented earlier or later than indicated or even features entirely not mentioned may be implemented.</p> <p>LedgerSMB is being developed as a <em>Core</em> system with many functionalities a business requires. However, some businesses may require different functionalities, or some functionalities may be considered too disruptive to integrate immediately into the core. These functionalities are developed as <em>Add-ons</em>.</p> <h1>Ready for next release</h1> <p>Completed developments which will be included in the next release, are listed in the <a href="https://github.com/ledgersmb/LedgerSMB/blob/master/Changelog#L6">Changelog</a> file. This page focusses on providing an overview of (desired) future change.</p> <h1>On-going</h1> <p>These functionalities are currently actively being worked on:</p> <ul><li>Webservices for posting invoices</li> <li>Conversion of the web-UI to Vue3</li> </ul><h1>Planned</h1> <p>The features in this section have been brought forward by existing contributors as items they want to work on (not necessarily in the stated order) when time permits. Some topics have been discussed between developers. None of these topics have seen any actual development just yet. If you're a developer interested to contribute to one of these topics, please step forward! We welcome contributions on each of these topics!</p> <ul></ul><h2>Improved (first) user experience</h2> <ul><li><a href="https://github.com/ledgersmb/LedgerSMB/projects/13">Re-implementing setup.pl</a></li> <li><a href="https://github.com/ledgersmb/LedgerSMB/projects/11" title="GitHub project #11">Improving the user experience on cash and payment handling</a></li> </ul><h2>Webservices for</h2> <ul><li>Retrieving and creating customers</li> </ul><h2>Completion of previously implemented features</h2> <ul><li><a href="https://github.com/ledgersmb/LedgerSMB/projects/9">Fixed assets</a></li> <li><a href="https://github.com/ledgersmb/LedgerSMB/projects/1">Overpayments</a></li> <li><a href="https://github.com/ledgersmb/LedgerSMB/projects/6">Inventory adjustments</a></li> </ul><h2>Internationalisation and localisation</h2> <ul><li>Better handling of plural forms</li> </ul><h2>Technical improvements</h2> <ul><li>Migrate remaining DBObject code to PGObject</li> <li>Much more unit and BDD testing</li> <li><a href="https://github.com/ledgersmb/LedgerSMB/projects/14">Number and currency formatting</a></li> </ul><h2>Accounting</h2> <ul><li><a href="https://github.com/ledgersmb/LedgerSMB/projects/4">Phase 2 of improved currency support</a>; e.g. foreign currency revaluation</li> </ul><h1>Wishlist</h1> <p>The following section lists highly desired features, grouped into topics. However, no developer has expressed any interest in working on these item in the foreseeable future. Developers who <em>do</em> want to work on these features, please step forward, we highly welcome contributions on these topics!</p> <h2>UI improvements</h2> <ul><li>Fewer defaults for configuration</li> <li>Layout improvements</li> <li>Help system</li> <li>Fully remodeled Contact entry screens</li> <li>Personal Dashboard</li> </ul><h2>Configuration and customization</h2> <ul><li>Easier development of templates by adding HTML-&gt;PDF output generator option</li> </ul><h2>Integration and scripting</h2> <ul><li>Web services</li> <li>Web hooks</li> </ul><h2>Accounting</h2> <ul><li>Revaluation of foreign currency balance sheet items</li> <li>Complete integration of pre/overpayments</li> </ul><h2>Goods and services</h2> <ul><li>(more/better) inventory reports</li> <li>production batch tracking</li> </ul><h2>Reporting</h2> <ul><li>Integrate budgets in financial reports</li> <li>Migrate reports module to Dojo/dgrid</li> </ul><h2>CRM</h2> <ul><li>Track events (like appointments) per customer, lead, etc.</li> <li>Sales Opportunity Tracking</li> <li>Sales forecasts</li> </ul><h2>HR</h2> <ul><li>Localization of <a href="http://permalink.gmane.org/gmane.comp.finance.ledger.smb.devel/3475" title="Sketching of Payroll">payroll roles</a> (implementation partner wanted!)</li> </ul><h2>Technical improvements</h2> <ul><li>Phase out code in old/ <ul><li>AR/AP invoices and transactions redesign</li> <li>GL transactions redesign</li> <li>Orders and Quotations redesign</li> <li>Warehouses, parts, and assemblies redesign</li> </ul></li> <li>Replacement of payments.pl</li> </ul><h2>Authorization</h2> <ul><li>Support for role groups</li> <li>LDAP and groupware integration</li> </ul><p> </p> </div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>Chris Travers</span></span> <span class="field field--name-created field--type-created field--label-hidden">Sat, 07/14/2012 - 01:11</span> <section class="field field--name-comment-node-page field--type-comment field--label-hidden comment-wrapper"> </section> Sat, 14 Jul 2012 08:11:36 +0000 Chris Travers 22 at https://ledgersmb.org https://ledgersmb.org/index.php/content/roadmap#comments Session expired immediately after logging in https://ledgersmb.org/index.php/faq/session-expired-immediately-after-logging <span class="field field--name-title field--type-string field--label-hidden">Session expired immediately after logging in</span> <div class="clearfix text-formatted field field--name-field-detailed-question field--type-text-long field--label-hidden field__item"><p>When I log in, LedgerSMB 1.8 or higher immediately says my session has expired. What can I do to fix this?</p> </div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>ehu</span></span> <span class="field field--name-created field--type-created field--label-hidden">Mon, 10/10/2022 - 09:49</span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>Short answer: add the "--preload-app" flag to the Starman command line.</p> <p>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.</p> </div> <div class="field field--name-field-component field--type-list-string field--label-above"> <div class="field__label">Component</div> <div class="field__item">Base</div> </div> <div class="field field--name-field-release field--type-entity-reference field--label-above"> <div class="field__label">Release</div> <div class="field__items"> <div class="field__item"><a href="/index.php/taxonomy/term/147" hreflang="en">1.8</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/149" hreflang="en">1.9</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/150" hreflang="en">1.10</a></div> </div> </div> <div class="field field--name-field-faq-category field--type-entity-reference field--label-above"> <div class="field__label">FAQ Category</div> <div class="field__item"><a href="/index.php/faq-categories/installation" hreflang="en">Installation</a></div> </div> <section class="field field--name-comment-node-faq field--type-comment field--label-hidden comment-wrapper"> </section> Mon, 10 Oct 2022 16:49:15 +0000 ehu 600 at https://ledgersmb.org https://ledgersmb.org/index.php/faq/session-expired-immediately-after-logging#comments Installing latest LedgerSMB using Docker Compose https://ledgersmb.org/index.php/content/installing-latest-ledgersmb-using-docker-compose <span class="field field--name-title field--type-string field--label-hidden">Installing latest LedgerSMB using Docker Compose</span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>By far the fastest procedure for installing LedgerSMB is by using the published Docker images: Being an ERP, there are many dependencies to be installed and all of them are included in the images, with the exception of the required PostgreSQL database. There are two ways to provide the PostgreSQL functionality: by setting up a separate PostgreSQL server or by using a PostgreSQL-providing Docker container.</p> <p>This article describes the latter option to use a second Docker container to provide the PostgreSQL server. The instructions below assume installed Docker and Docker Compose. Many tutorials to install them float around on the web; e.g. <a href="https://www.digitalocean.com/community/tutorials/how-to-install-docker-compose-on-debian-9">these instructions from DigitalOcean to install docker-compose</a>.</p> <ol><li>git clone https://github.com/ledgersmb/ledgersmb-docker.git<br /> This checks out the docker-compose file which will install the latest production version; if you want to use an older version, e.g. 1.6, add the -b &lt;version&gt; option:<br /> git clone -b 1.6 https://github.com/ledgersmb/ledgersmb-docker.git</li> <li>cd ledgersmb-docker</li> <li>docker-compose pull</li> <li>docker-compose up -d<br /> Note that the "-d" is important: it starts the containers in the background; without it, the containers' logs will be shown in the terminal. They can be terminated with Ctrl-C, but that also terminates the containers<br /><br /> After the steps above, LedgerSMB should be available on http://127.0.0.1:5762/</li> <li>apt-get install apache2 certbot python-certbot-apache</li> <li>certbot certonly  --apache -d example.com -d www.example.com</li> <li>grab the &lt;site&gt;.conf from the LedgerSMB code repository and edit it: <ol><li>curl https://raw.githubusercontent.com/ledgersmb/LedgerSMB/master/doc/conf/webserver/apache-vhost.conf -o /etc/apache2/sites-available/ledgersmb.conf</li> <li>nano /etc/apache2/sites-available/ledgersmb.conf: <ol><li>Replace YOUR_SERVER_NAME with your server name; e.g. "example.com"</li> <li>Replace SSL_CERT_FILE, SSL_KEY_FILE, and SSL_CHAIN_FILE with the corresponding files in /etc/letsencrypt/live</li> <li>Replace http://localhost:5762 with http://127.0.0.1:5762<br /> When your server has IPv6 enabled, the former will resolve to ::1, on which the container created above, isn't available</li> <li>Finally, remove the DocumentRoot line with WORKING_DIR</li> </ol></li> </ol></li> <li>a2ensite ledgersmb</li> <li>a2enmod ssl rewrite proxy proxy_http</li> <li>systemctl restart apache2</li> </ol><p> </p> <p> </p> </div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span>ehu</span></span> <span class="field field--name-created field--type-created field--label-hidden">Sat, 06/20/2020 - 04:48</span> <div class="field field--name-field-topic field--type-entity-reference field--label-above"> <div class="field__label">Topic</div> <div class="field__items"> <div class="field__item"><a href="/index.php/topic/installation" hreflang="en">Installation</a></div> </div> </div> <div class="field field--name-field-release field--type-entity-reference field--label-above"> <div class="field__label">Release</div> <div class="field__items"> <div class="field__item"><a href="/index.php/taxonomy/term/142" hreflang="en">1.6</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/146" hreflang="en">1.7</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/147" hreflang="en">1.8</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/149" hreflang="en">1.9</a></div> <div class="field__item"><a href="/index.php/taxonomy/term/150" hreflang="en">1.10</a></div> </div> </div> <section class="field field--name-comment-node-article field--type-comment field--label-hidden comment-wrapper"> </section> Sat, 20 Jun 2020 11:48:09 +0000 ehu 472 at https://ledgersmb.org https://ledgersmb.org/index.php/content/installing-latest-ledgersmb-using-docker-compose#comments