- users - lists.freelock.com

Running LedgerSMB 1.5 with a schema other than public
by Nicolas Couchoud 18 Aug '19

18 Aug '19

Hi, In my current installation of LedgerSMB, the tables are in a schema other than public, because I installed it in a database where there are other data in schema public. (The reason I did that is that I want to link tables in schema public and LedgerSMB tables, but I have not done it yet.) I could make it work relatively painlessly with LedgerSMB 1.3 by setting db_namespace in ledgersmb.conf. Recently (that is, very late!) I wanted to upgrade to LedgerSMB 1.5.24 (not 1.6 because my server is still under Debian stretch). I think I could upgrade the database correctly with setup.pl, but when running login.pl it will not work because, according to Postgresql's logs, it insists on trying to call the stored procedure public.setting_get, which does not exist. Although I do not know perl, I tried to read the code to understand what is going on. If I understood well, stored procedures are called by calling directly or indirectly the perl function call_procedure in module PGObject, which sets the schema to public when it is not specified. However, module LedgerSMB also contains a function call_procedure which correctly sets the schema, so the problem seems to be that sometimes PGObject's call_procedure is called directly instead of module LedgerSMB's. I do not understand why, because I do not know what constructs like $self->call_procedure or __PACKAGE__->call_procedure do, but anyway this is very annoying for me, because it means that LedgerSMB 1.5 just will not work with db_namespace set to anything else than public. Was this problem known? Is it corrected in a later version? Regards.

2 6

Virtualbox image with LSMB 1.6.10
by Pongrácz István 07 Jul '19

07 Jul '19

Hi, I just created a fresh virtualbox image to install ledgersmb 1.6.10 on it. It is really a basic image: - Ubuntu 18.02 Server, updated on 6th of Jun, 2019 - added ppa:ledgersmb - added postgresql repository (pgdg.list) - postgresql 11 installed - ledgersmb 1.6.10 installed, listens on *:5762 - created on Virtualbox 6.0, exported as OVA, basic information included in description (login etc.), 1.7GB packed size Todo after starting (only quick hints): - set up network - change users/passwords - recreate ssh server keys - whatever Where can I upload officially? Cheers, István

2 2

LedgerSMB 1.7.0-beta1 released
by Erik Huelsmann 01 Jul '19

01 Jul '19

Hi, After the release of 1.7.0-alpha1 we have been working towards the 1.7.0 release as described in our community update. We feel that the 1.7.0 branch is feature complete and while we're developing tests to find and fix possible regressions and older bugs, no new features or major changes are expected to be implemented before 1.7.0. This means that the current code base (modulo any and all regressions we can find and fix) will become 1.7.0 when it's ready. To help you find the bugs we need to fix before the release, we have published 1.7.0-beta1. It's available as a Docker image from Docker Hub under the tag "ledgersmb/ledgersmb:1.7.0-beta1". See https://hub.docker.com/r/ledgersmb/ledgersmb/builds/ Additionally, the release can be downloaded as a tarball from the download site: https://download.ledgersmb.org/f/Beta%20Releases/1.7.0-beta1/ Please report any issues you find in reply to this e-mail (that is, to the mailing list) or create an issue on GitHub with your finding: https://github.com/ledgersmb/LedgerSMB/issues/new?template=ISSUE_TEMPLATE.md -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

LedgerSMB community update
by Erik Huelsmann 01 Jul '19

01 Jul '19

Hi, It was just before New Year when I sent out the last community update, so it's time for a follow up. This half year, we only released 1 maintenance release for 1.6.10. With no specific new bug reports coming in, the development team was able to focus its efforts on 1.7.0. On that front, a lot of development effort has gone into getting the Multi-Currency branch ready to be merged to master. On January 20th the long-awaited multi-currency branch merge happened, followed by the release of 1.7.0-alpha1. Since then, we've been developing more tests simulating user interaction with LedgerSMB to ensure that 1.7.0 will be as good as 1.6.0 when it is released. In the process, we have been fixing a few regressions. With the additional tests - which include tests for AR & AP invoices and transactions - we have increased test coverage from 29% (current on 1.6) to 40% (on master) and we're working to increase the number to well above 50% before release. The speed at which we're able to implement new tests is severely impacted by the fact that we hit a continuous integration limit: Travis CI allows us to run tests for a maximum of 50 minutes. Our test suite runs between 40 and 45 minutes in code-coverage testing mode. A lot of effort has gone into working on this problem. We're working to off-load the code-coverage test jobs to another Continuous Integration service (CircleCI) which *does* allow jobs to run longer than 50 minutes. Another direction of research was to reduce execution time of our test jobs. And while that did turn up some bugs in our Selenium test driver, it mainly helped the area where we didn't experience any problems (the non-code-coverage tests were reduced from 29-30 minutes of execution to 20-21 minutes of execution). Migrating some of our test infrastructure to CircleCI turned out to have the additional benefit of being able to start running our tests against Chrome and Firefox. Currently we only run against PhantomJS. While PhantomJS implements enough of JavaScript to support our testing, it's unmaintained and getting behind on recent standards. Being able to test with Chrome and Firefox will help to take advantage of more modern browser development techniques. As part of our optimization work, we helped create new releases of Weasel, Pherkin::Extension::Weasel and Test::BDD::Cucumber, where significant new features were added to Pherkin::Extension::Weasel to support increased developer efficiency. Looking to the immediate future, we're expecting to release 1.7.0-beta1 this week: we think 1.7.0 is feature complete and we'll work simply to stabilize it from here on. This means that 1.7.0 isn't production ready, but we're looking for people to test-drive it and value any and all bug reports we can get! Regards, Erik. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

Re: [ledgersmb-users] Fwd: Fwd: Production Install, Networking and Setup
by Robert J. Clay 17 May '19

17 May '19

On Sat, May 4, 2019 at 1:52 AM Xboxboy Mageia <xboxboy.mageia(a)gmail.com> wrote: >> > the browser wont go to http://LedgerSMB/setup.pl Did you tell the system on which the browser is running, which IP that 'LedgerSMB' name has? Or put it your local DNS? Also; if you're using the default setup, you should be using "https", not "http". And note (in case you don't already know) that browsers like Chromium really don't like using https with ssl certs like what we're using by default (a valid ssl cert but not one that is registered where the browser knows of), but how you get around that and still get the secure session depends on the browser. (But yes, despite such dns & ssl issues, we still recommend using secure broswer session to access the LSMB app.) > I tried adding the machines IP as the servername, but that didn't work either. In what way did you try adding it? In the URL? For instance, although I also have LXCs/VMs running on a local server, I usually have test containers running on my laptop. And don't have the networking where those are running accessible outside of the laptop. So rather than adding the server name for the LXC to the DNS on the laptop (since the IP can change depending on what other containers have been started), I just use the IP. For example; if 10.0.0.231 is the IP, then for the LSMB setup login page I would use https://10.0.0.231/setup.pl. Or, https://10.0.0.231/login.pl for the login page. -- Robert J. Clay rjclay(a)gmail.com

2 5

LEDGERSMB on Windows 10
by Terry Mcgrane 12 May '19

12 May '19

Hi all I sure as hell hope someone can help me. I have been looking at LedgerSMB now for 2 weeks trying to figure out how I get this working on a Windows10 PC, and damned if i understand any of it. I so would love to use this software, sick of paying out thousands of dollars each year for not much. Ledger SMB from what I have read and seem on the youtube is perfect it does everything i want and more. Is there anyone out there that would be willing to give me a hand setting it up on my PC using TEAMVIEWER. I live in Australia so you would have to consider the time difference. I am hoping to do this ASAP so if there is any I would really appreciate your help. Thank you Terry

2 1

Creating Docker Instance of LSMB
by Ryle Zabate 05 May '19

05 May '19

Greetings!Hello Team, upon configuring the docker command: docker-compose up, i did encounter the following error below: Starting ledgersmb2019_postgres_1 ... errorERROR: for ledgersmb2019_postgres_1 Cannot start service postgres: network f3a4c456e824f5462dfdedcbb29d41668863f1540aded7bc5c3bd93c2cbec085 not foundERROR: for postgres Cannot start service postgres: network f3a4c456e824f5462dfdedcbb29d41668863f1540aded7bc5c3bd93c2cbec085 not foundERROR: Encountered errors while bringing up the project.PS C:\Windows\System32\ledgersmb2019> For your kind assistance on how could i successfully run an instance of LSMB thru Docker image. Warm Regards,/ITD/ Ryle.Msinc/ITDept

1 1

Re: [ledgersmb-users] Fwd: Fwd: Production Install, Networking and Setup
by Xboxboy Mageia 03 May '19

03 May '19

Apologies Robert, gmail frustratingly doesn't auto-reply to group :( On Sat, May 4, 2019 at 3:22 PM Xboxboy Mageia <xboxboy.mageia(a)gmail.com> wrote: > > > On Mon, Apr 22, 2019 at 7:57 AM Robert J. Clay <rjclay(a)gmail.com> wrote: > >> >> >> The example LSMB distribution file 'apache-vhost.conf' is installed >> by the pkg as 'ledgersmb-1.5-proxy.conf' to the >> /etc/apache2/sites-available/ directory. >> >> Much of that file is already configured by default by the pkg, but >> the 'ServerName' item is not configured by default (which is why the >> pkg install does not curently attempt to enable the config file by >> default). Once that is set, on Debian you can enable it by using >> something like: >> >> Using the command "hostname" I get "LedgerSMB" > I've added that to the ledgersmb-1.5-proxy.conf file > > >> a2ensite ledgersmb-1.5-proxy.conf >> >> No complaints > > >> If that doesn't come up with any issues, then: >> >> systemctl reload apache2 >> >> If no issues come up, you can try accessing the LSMB setup page by >> going to https://server.name.com/setup.pl (or you could try via the >> IP...) >> >> the browser wont go to http://LedgerSMB/setup.pl > > So, I'm tripped up again: Sorry. > > I tried adding the machines IP as the servername, but that didn't work > either. > > Any questions/comments/concerns etc, please let us know. >> >> >> Thanks for your patience... I will get there though. > >> >> -- >> Robert J. Clay >> rjclay(a)gmail.com >> >

1 0

Fwd: Fwd: Production Install, Networking and Setup
by Xboxboy Mageia 21 Apr '19

21 Apr '19

Bill, yes, sorry that is a typo: I meant http://192.168.1.118:5762/setup.pl Regards, Xboxboy ---------- Forwarded message --------- From: bill Ott <billott(a)theotts.org> Date: Thu, Mar 21, 2019 at 1:21 AM Subject: Re: [ledgersmb-users] Fwd: Production Install, Networking and Setup To: Xboxboy Mageia <xboxboy.mageia(a)gmail.com> http://192.168.1.*188*:5762/setup.pl???? Did you mean http://192.168.1. *118:*5762/setup.pl? Regards, Bill Ott Home: 919-363-0031 Cell: 919-434-7589 Email: Mailto:billott@theotts.org <billott(a)theotts.org> Website: http://www.theotts.org Profile: http://www.linkedin.com/in/wbott On 3/19/19 9:47 PM, Xboxboy Mageia wrote: Sorry Bill: I meant to send it to the list :-0 Please see the network info I've added, in response to both Bill and Erik. On Mon, Mar 18, 2019 at 6:45 PM Xboxboy Mageia <xboxboy.mageia(a)gmail.com> wrote: > Hello, > I was sick over Xmas, and since then business has been booming, only now > can I have a second look. Thank you all for you help. > > > On Thu, Jan 10, 2019 at 10:38 AM bill Ott <billott(a)theotts.org> wrote: > >> Running "brctl show" w/o/ the quotes on the VM's host will show you the >> bridge and the interfaces that are connected to it. 'ifconfig" w/o the >> quotes on the VM's host will show you the all of interfaces. >> > brctl show > bridge name bridge id STP enabled > interfaces > virbr0 8000:525400da324e yes > virbr0-nic > > ifconfig > > enp5s0 is on 192.168.1.109 > lo is on 127.0.0.1 > virbr0 is on 192.168.122.1 > > (sorry can't ssh in at the moment, let me know if you need all the details) > > Might help chasing down the problem. >> >> Regards, >> Bill Ott >> >> Home: 919-363-0031 >> Cell: 919-434-7589 >> Email: Mailto:billott@theotts.org <billott(a)theotts.org> >> Website: http://www.theotts.org >> Profile: http://www.linkedin.com/in/wbott >> >> On 1/9/19 5:21 PM, Erik Huelsmann wrote: >> >> Hi, >> >> 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. >>> >> >> [snip] >> >> >>> 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. >>> >> >> Ok. Are you able to ping that ip address from your desktop? That should >> indicate if you should expect to be able to connect to the web server as >> well. >> >> >> Yes, I can ping the debian VM with "ping 192.168.1.118" > I can access the default debian apache web server at 192.168.1.118, but no > luck with 192.168.1.188:5762/setup.pl > > I have a functioning fedora os VM on 192.168.1.107 with nextcloud working > fine. > > >> 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. >>> >> >> Bridged sounds fine. quick question: Is the "eth0" (or enpXs0 with X a >> number) network on the VM's host part of the bridge? If not, you probably >> need to enable IP forwarding. Before we go that route, lets start by >> checking you can 'ping' the address though. (And: can you ping the host >> that the VM is running on?) >> >> I can ping the host with "ping 192.168.1.109" > >> >> >>> >>> All advice appreciated. >>> >> >> Regards, >> >> -- >> Bye, >> >> Erik. >> >> http://efficito.com -- Hosted accounting and ERP. >> Robust and Flexible. No vendor lock-in. >> >> _______________________________________________ >> users mailing listusers@lists.ledgersmb.orghttps://lists.ledgersmb.org/mailman/listinfo/users >> >> _______________________________________________ >> users mailing list >> users(a)lists.ledgersmb.org >> https://lists.ledgersmb.org/mailman/listinfo/users >> > _______________________________________________ users mailing listusers@lists.ledgersmb.orghttps://lists.ledgersmb.org/mailman/listinfo/users

4 9

Are there any subscribers using LedgerSMB versions older than 1.4?
by Erik Huelsmann 06 Apr '19

06 Apr '19

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.

3 5