- users - lists.freelock.com

Fwd: Debian packages for LedgerSMB
by Robert J. Clay 11 Jan '19

11 Jan '19

Forgot to cc this to the mailing list... ---------- Forwarded message --------- From: Robert J. Clay <rjclay(a)gmail.com> Date: Tue, Jan 1, 2019 at 2:16 PM Subject: Re: [ledgersmb-users] Debian packages for LedgerSMB To: Nicolas Couchoud <nicolas.couchoud__ledgersmb(a)normalesup.org> Hi Nicolas! On Mon, Dec 31, 2018 at 10:07 AM Nicolas Couchoud <nicolas.couchoud__ledgersmb(a)normalesup.org> wrote: > > Hi, > > As far as I have understood, there are two sorts of Debian packages for > LedgerSMB : > * Debian regular repositories just contain packages called « ledgersmb » ; Yes, that's the official Debian package for the LedgerSMB application (which also migrates over to the developmental version of Ubuntu). The most recent is the one for the most recently released version of LedgerSMB, 1.6.9. (Released just a few days ago.) > * your repository apt.ledgersmb.org contains packages with names like > « ledgersmb-1.5 » and « ledgersmb-1.5-apache ». Yes, the ledgersmb-1.5 packages are for the 1.5.x versions of LedgerSMB, with the latest being v1.5.24 (just released a few days ago). The ones like ledgersmb-1.5-apache are for web proxies if one wants to use one. The 1.5.x versions will be supported by the project until December of this year (2019) when it will see its End Of Life for community support.. There are also the ledgersmb-1.6 packages, which are for the 1.6.x versions of the LedgerSMB application (the current stable). It also has the associated packages for a web proxy selection. > So, I feel a bit lost... Is there one preferred sort of package ? Are > some of these obsolete ? The ledgersmb-1.5 packages aren't "obsolete" but they are for the old-stable version of LedgerSMB (1.5.x), which as noted will see End of Life in December 2019. (Whereas the 1.6.x versions are good for LedgerSMB Community Support until December of 2021.) Their advantage is that due to the availability of dependencies, the ledgersmb-1.5 packages can be backported to older versions of Debian (or Ubuntu) than the ledgersmb-1.6 packages currently can be. The primary difference between the 'ledgersmb' package and the 'ledgersmb-1.x' packages is that due to Debian Policy (regarding embedded libraries), the ledgersmb packages uses the system installed packages for the Dojo libraries while the ledgersmb-1.x packages use the embedded versions of the Dojo libraries that are released with each version of the LedgerSMB application. -- Robert James Clay rjclay(a)gmail.com, jame(a)rocasa.us -- Robert J. Clay rjclay(a)gmail.com

1 0

Re: [ledgersmb-users] users Digest, Vol 20, Issue 1
by Ryle Zabate 11 Jan '19

11 Jan '19

Hi, thank you for your question. On our case, we are still using the 1.3.46 release since the only available pdf manual is only for 1.3 version.Can we now migrate to higher versions of LSMB without any issues and retaining the data of the 1.3 setup? Regards. Ryle.Msinc/ITDept From: "users-request(a)lists.ledgersmb.org" <users-request(a)lists.ledgersmb.org> To: users(a)lists.ledgersmb.org Sent: Wednesday, January 2, 2019 4:00 AM Subject: users Digest, Vol 20, Issue 1 Send users mailing list submissions to users(a)lists.ledgersmb.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.ledgersmb.org/mailman/listinfo/users or, via email, send a message with subject or body 'help' to users-request(a)lists.ledgersmb.org You can reach the person managing the list at users-owner(a)lists.ledgersmb.org When replying, please edit your Subject line so it is more specific than "Re: Contents of users digest..." Today's Topics: 1. Are there any subscribers using LedgerSMB versions older than 1.4? (Erik Huelsmann) ---------------------------------------------------------------------- Message: 1 Date: Tue, 1 Jan 2019 15:41:24 +0100 From: Erik Huelsmann <ehuels(a)gmail.com> To: users(a)lists.ledgersmb.org Subject: [ledgersmb-users] Are there any subscribers using LedgerSMB versions older than 1.4? Message-ID: <CACOoB6jUCbQsvB+oL3XSp=9jR=ZN0LpU0ady3Sz+uHGSGM37_Q(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi all, Migrations have become considerably more controlled since the 1.5 release, which introduces a smooth migration from 1.4. As such migration paths do not exist for 1.1, 1.2 and 1.3, I'm eager to learn if there are any users out there of these old versions, and, if you're not migratiing, what's keeping you from doing so. If you can't publicly respond to this inquiry, please mail me privately so I can treat your information confidentially. Thanks for your responses, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

Exchange Rate
by Ryle Zabate 11 Jan '19

11 Jan '19

Hello Team, I need your expert advice for this subject.How can we set the exchange rates if the currency is different form our country default currency,Let's say the purchase order is to be sent to another country. Your help is greatly appreciated. Regards. Ryle.Msinc/ITDept

1 0

Re: [ledgersmb-users] Production Install, Networking and Setup
by Xboxboy Mageia 10 Jan '19

10 Jan '19

On Sat, Dec 29, 2018 at 11:28 AM Xboxboy Mageia <xboxboy.mageia(a)gmail.com> wrote: > Erik, thanks for responding. > > On Mon, Dec 24, 2018 at 9:43 PM Erik Huelsmann <ehuels(a)gmail.com> wrote: > >> Hi! >> >> Good! Feel free to drop in whenever you feel like it. The channel may not >> always be active, but I'm usually monitoring activity. You're most likely >> active during my nights (I'm in Europe), but I'll try to respond as early >> on the day as possible. >> > I forgot to mention, I'm on IRC these days as Aussie_matt (registered > name) or pilot_aus (unregistered). > >> >> >> Ok. So, I take it your desire is to run the setup in the Debian VM? Or >> are you looking at installing in a CentOS VM? >> >> Sorry, yes, I'll use a Debian OS guest VM, on a Centos host OS. > >> >> Sure. No problem. Is the server which hosts the VMs web-facing? (Hmm, >> reading on, I think your point with the fixed IP is probably that it is >> webfacing indeed.) >> > Not currently, I only have it running internally on our network: But I > wish to have LedgerSMB, and one other web app, to be accessible from > outside: I don't know the ins and outs of VPN's, but I suspect that makes > it tricky for the accountant to login. Web facing is more practical, but > more open to web threats? I could be wrong on that. > >> >> >>> I would like LedgerSMB to be web facing to allow me to >>> A: work from home at times >>> B: The accountant to log in and work when required (usually year end). >>> >> >> I have a setup like that myself too, so we can make that work :-) >> >> Awesome! > >> Which version of LedgerSMB did you install? Do I remember that you're >> installing 1.5? >> >> I believe you're correct it was 1.5, as the apt repo wasn't able to do > 1.6 for some reason at this point in time: Dependency related IIRC. > >> >>> All advice most appreciated. I may need my hand held significantly at >>> first, especially in regards to networking and security. >>> >> >> In order to run a secure setup, there's one very important thing you need >> to have: a TLS/SSL Certificate. That will help keep the password going over >> the wire, secure. >> Another thought that I have is: when you want to expose only LedgerSMB's >> web interface to the outside world, it's probably best to set up an >> extremely strict firewall/iptables setup which forwards/filters just the >> one single required port. Another idea would be to set up a (reverse) >> proxy: an HTTP server running on an already public VM which forwards the >> traffic to an internal server unaccessible to the internet. >> >> Ah yes. Ok, so on my home Nextcloud install (internal only) I was able to > create and use a self signed cert, but if we're going net facing, and the > accountant is going to access it, I'm guessing using Let's Encrypt or > similar is worth chasing up? > I'm all for locking firewalls down tight: I still don't fully understand > the reverse proxy concept: But I'm sure I can be guided :) > > >> Many ideas. Please follow-up or join #ledgersmb! >> >> I've come down sick over the break, so am yet to return to the shop to > look at doing anything: > > I guess my first step is to install a Debian OS vm, and get the APT repo > hooked in and installed: Take a snapshot, then we can proceed? > > Ok, so the debian install went simply. I used debian 9 (Stretch), without a GUI. 'ip addr' gives 192.168.1.101, which sounds right, as that's my lan, 192.168.1.X. I then followed the instructions on https://apt.ledgersmb.org/index.html, but I installed version 1.5, and did not add the 'test component', I don't know what that means, sorry. > Regards, >> >> -- >> Bye, >> >> Erik. >> >> Many thanks. > >> http://efficito.com -- Hosted accounting and ERP. >> Robust and Flexible. No vendor lock-in. >> > I was able to add the DB admin user where the prompt comes up: Now do I need to reset/config mysql's root user and password also? So from my desktop I tried to access via firefox 192.168.1.101:5762/setup.pl, but it's unable to connect. I have the VM network set to bridged, networking is my downfall, and the other thing I suspect is that I need to open the firewall for the webserver. All advice appreciated.

4 3

LedgerSMB Concerns (Accounts Receivable)
by Bernadette Nicole Rivera 02 Jan '19

02 Jan '19

Hi Team, I'm one of the Administrator of LedgerSMB System here in the Philippines. We have concerns with regards to the Accounts Receivable, we were unable to delete VOID INVOICED(wrong inputs) and Invoiced (due to wrong inputs of the sequence of the invoice number). Please see attached file for your reference. Hoping for your quick response for this matter. Thank you, -- Best Regards, *Bernadette Nicole C. Rivera IT Support L1 * Multistyle Specialist Inc. +639289698563 / (02) 641-6515 --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 10

Debian packages for LedgerSMB
by Nicolas Couchoud 31 Dec '18

31 Dec '18

Hi, As far as I have understood, there are two sorts of Debian packages for LedgerSMB : * Debian regular repositories just contain packages called « ledgersmb » ; * your repository apt.ledgersmb.org contains packages with names like « ledgersmb-1.5 » and « ledgersmb-1.5-apache ». So, I feel a bit lost... Is there one preferred sort of package ? Are some of these obsolete ? Regards.

1 0

Release of Debian packages for LedgerSMB v1.6.9
by Robert J. Clay 29 Dec '18

29 Dec '18

An initial version of the Debian ledgersmb package for version 1.6.9+ds-1 has been released and uploaded to Debian: I anticipate it migrating to Debian Testing ("Buster") by next week (the announcement for which will be posted to the devel list) and also over to the current developmental Ubuntu version (which will be for v19.04). It has also been uploaded to our PPA[1] as version 1.6.9-1 of the ledgersmb-1.6 package: for 'cosmic' (v18.10) as well as 'bionic' (v18.04 LTS). (The Debian source packages are available as well.) The packages at our PPA: ledgersmb-1.6 ledgersmb-1.6-apache ledgersmb-1.6-lighttpd ledgersmb-1.6-nginx ledgersmb-1.6-varnish Only the main 'ledgersmb-1.6' package is required; the others are related to which web proxy you might want to use and you only need one of them. -- Robert J. Clay rjclay(a)gmail.com, jame(a)rocasa.us GPG ID: 2448 3AE0 874D 8696 6DCD ECF4 198C AB6F 43B7 EA9A. [1] https://launchpad.net/~ledgersmb/+archive/ubuntu/main/+packages

1 0

Release of ledgersmb-1.5 v1.5.24-1
by Robert J. Clay 29 Dec '18

29 Dec '18

An initial version of the debian ledgersmb-1.5 package for version 1.5.24-1 has been released and uploaded to our apt package repository for 'main' in stretch[1]. It has also been uploaded to our PPA[2], for 'cosmic' (v18.10) as well as 'xenial (v16.04 LTS) and 'bionic (v18.04 LTS). (The Debian source packages are available as well.) The packages at both our apt package repository and our PPA: ledgersmb-1.5 ledgersmb-1.5-apache ledgersmb-1.5-lighttpd ledgersmb-1.5-nginx ledgersmb-1.5-varnish Only the main 'ledgersmb-1.5' package is required; the others are related to which web proxy you might want to use and you only need one of them. Note also that 1.5.x release series will be supported up through December of 2019. -- Robert J. Clay rjclay(a)gmail.com, jame(a)rocasa.us GPG ID: 2448 3AE0 874D 8696 6DCD ECF4 198C AB6F 43B7 EA9A. [1] https://apt.ledgersmb.org/ [2] https://launchpad.net/~ledgersmb/+archive/ubuntu/main/+packages

1 0

LedgerSMB Concerns (Cash -> Receipts)
by Nicole Rivera 27 Dec '18

27 Dec '18

Hi Team, Good day! Every time I clicked POST AND PRINT on the Receipts the error occurs: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator at webmaster@localhost to inform them of the time this error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log. ------------------------------------------------------------------------ Apache/2.4.18 (Ubuntu) Server at 192.168.1.18 Port 80 Please help us to solve this problem, thank you! -- Best Regards, *Bernadette Nicole C. Rivera IT Support L1 * Multistyle Specialist Inc. +639289698563 / (02) 641-6515 --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1

LedgerSMB community overview 2018
by Erik Huelsmann 27 Dec '18

27 Dec '18

Here's my continuing the tradition to write about the state of the project on each year end. == Community interest == With the growth of the number of places to obtain LedgerSMB, it's becoming increasingly more difficult to estimate the project popularity. We're now available through at least the following channels: Distribution packages (Debian repository, Ubuntu ppa, our own Debian/Ubuntu repository), Docker images on Docker Hub (with docker-compose support), regular 'tar file' download through GitHub or our own download site. Many of these sources don't track stats for hits, or at least those stats aren't available to us. A notable fact though is that the Google and Yahoo searches 'open source accounting' serve as the top hits a number of pages which cite or refer to LedgerSMB. Based on the steady stream of issues being logged on our GitHub issue tracker, the fact that the number of forks and stars (as well as watches) are steadily growing and the number of Docker Hub downloads is steadily increasing, I'd say that we get a fair amount of attention and our community is continuing to find people interested. == Releases == Last year's community overview looked forward to 2018 and expressed the hope to release LedgerSMB 1.6 in the first half of the year. And we did: June 10th we released 1.6.0 -- little less than a 18 months after 1.5.0! As expected, we were able to further shorten the time between releases. This year, we haven't topped last year's 20 releases. With 20 releases, the year can definitely be called succesfull though. We released: - 10 stable releases: 1.6.0 - 1.6.9 - 10 old-stable releases: 1.5.15 - 1.5.24 Releases hardly ever contain fixes for regressions anymore. That's to say, regressions for functionality that worked in a recent release. Regressions being fixed went back to functionality being broken before 1.5.0 and sometimes even during the 1.3 or earlier release cycles(!). In addition to the 18 releases, significant new infrastructure landed on the master branch which helps advance the project to higher levels. An excerpt of all the work done includes further extension of the testing framework, separation of the template frameworks for UI and 'printed' materials and lots of minor and major code cleanups. In addition to generating releases, each year some effort is spent on release engineering; this year, we further automated the release announcements by automatically posting the news updates on github.com and ledgersmb.org (using the same announcement text as is used for the mail announcements). == Packaging and installation == The Debian+Ubuntu packages now include a new 'ledgersmb-1.6' package. The packaging process keeps improving, because by the end of the year, new packages were announced within 24 hours after the release of the new LedgerSMB version. With the introduction of the LedgerSMB 1.6 Docker builds, further energy was spent in shrinking the images. We started the year with images around 250MB in size (reported by Docker Hub); by the end of this year, images for 1.6 are showing less than 180MB and those for 1.5 around 160MB in size. That's another significant reduction. == Development progress == Over the course of 2018, 107 issues were created, of which 35 remain open at the end of the year (of which 8 enhancements); 126 issues were closed. More than 470 pull requests were created and 479 were closed. These numbers are significantly lower than last year, which is probably due to lower development activity (especially in the master branch) over the course of the second half year. However, the general feeling is that we are also continuing the trend of last year: due to the fact that the code base is increasingly more stable, there's more time to work on the more involved projects: those that (prepare to) refactor the code base. This work, while necessary, doesn't immediately produce commits or PRs. Last year, we set aside the code that we want to part with in the source tree, signalling to (potential) contributors which parts need improvement and which need replacement. Consensus has it that this distinction has lowered the barrier of entry by offering a relatively clean code base to newbee developers and this has in fact been a reason for this some of the activity of this year's contributors. In 2018, we ran over 1250 builds (starting at 6091; currently at 7354 and counting), but more importantly, we increased our test coverage from 27.48% to a current coverage of 34.22% (thanks Travis CI for all the donated compute time and Coveralls for the stats and analysis interface!). While we definitely have more code to cover to get to an acceptable coverage level, this is a very welcome increase! Areas which received extensive attention beyond that which has already been published through the 1.6 release notes include: - work to explore the benefits of moving our code base to Dancer2 - work to identify the roadmap to merging the MC (multi-currency) branch, including work to - re-implementing some of the changes on the branch to adopt new paradigms as on 'master' - implement checks, balances and tools to help people migrate their data to MC on upgrade - work to de-couple frontend and backend implementations, even before there is a web API - work to explore what needs to be done to support a REST API == New functionality and improvements == This year we added relatively little truely new functionality to the code base. Most effort was spent improving it. One thing worth mentioning in this area is the fact that we added tests to assert that modules (at the very least those we intend to keep) comply with a minimum level of documentation -- we set the documentation standard through Perl::Critic rules and we'll work toward increasing the standard over the next year, most likely. == Looking forward to 2019 == Ideally, we'll see the 1.7 release in the first half of 2019: that would shorten our release cycle to the much-desired yearly interval. Releasing by the end of the first half year puts businesses in a good position to test the software before running the year-end figures (assuming most businesses do so by the end of the calendar year). This year will likely be the year to land the MC branch effort on master, too. A lot of work has gone into preparation for this step and more work - following a precise checklist - is under way. Wether this functionality lands before 1.7 or after, is yet to be decided. Stability comes before anything else and we don't want to break our upward trend in that area. (Although some instability is to be expected after a subject this big lands on master, I'd like to have it stabilized before release.) For 2019, I wish the project finds one or two new contributors and our community has the patience to wait for MC to land before we continue into (also) highly desired areas such as a REST API -- to help the project to focus, that is. Then, lastly, let me finish by wishing everybody in our community a very good 2019 and by stressing that we'll welcome everybody who wants to contribute to our efforts (be it in development, testing, translating, documenting, coaching or sponsoring)! -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0