Fwd: Fwd: Production Install, Networking and Setup
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@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@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@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@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@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@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@lists.ledgersmb.org https://lists.ledgersmb.org/mailman/listinfo/users
_______________________________________________ users mailing listusers@lists.ledgersmb.orghttps://lists.ledgersmb.org/mailman/listinfo/users
Have you tried temporarily turning off SELinux ("setenforce 0"), then trying to connect? After doing the test, turn SELinux back on with "setenforce 1". Regards, Bill Ott Home: 919-363-0031 Cell: 919-434-7589 Email: Mailto:billott@theotts.org Website: http://www.theotts.org Profile: http://www.linkedin.com/in/wbott On 3/21/19 3:40 AM, Xboxboy Mageia wrote:
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@theotts.org <mailto:billott@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@gmail.com <mailto:xboxboy.mageia@gmail.com>>
http://192.168.1.*188*:5762/setup.pl?? <http://setup.pl??>?? Did you mean http://192.168.1.*118:*5762/setup.pl <http://setup.pl>? Regards, Bill Ott
Home: 919-363-0031 Cell: 919-434-7589 Email:Mailto:billott@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@gmail.com <mailto:xboxboy.mageia@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@theotts.org <mailto:billott@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 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 <http://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 <http://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 <http://efficito.com/> -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
_______________________________________________ users mailing list users@lists.ledgersmb.org <mailto:users@lists.ledgersmb.org> https://lists.ledgersmb.org/mailman/listinfo/users
_______________________________________________ users mailing list users@lists.ledgersmb.org <mailto:users@lists.ledgersmb.org> https://lists.ledgersmb.org/mailman/listinfo/users
_______________________________________________ users mailing list users@lists.ledgersmb.org <mailto:users@lists.ledgersmb.org> https://lists.ledgersmb.org/mailman/listinfo/users
_______________________________________________ users mailing list users@lists.ledgersmb.org https://lists.ledgersmb.org/mailman/listinfo/users
On Thu, Mar 21, 2019 at 11:00 PM bill Ott <billott@theotts.org> wrote:
Have you tried temporarily turning off SELinux ("setenforce 0"), then trying to connect? After doing the test, turn SELinux back on with "setenforce 1".
Thanks Just tried that on the host OS with no change. The debian VM doesn't have SElinux installed, as 'getenforce' and 'sestatus' return command not found. Regards,
Bill Ott
Home: 919-363-0031 Cell: 919-434-7589 Email: Mailto:billott@theotts.org <billott@theotts.org> Website: http://www.theotts.org Profile: http://www.linkedin.com/in/wbott
On 3/21/19 3:40 AM, Xboxboy Mageia wrote:
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@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@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@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@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@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@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@lists.ledgersmb.org https://lists.ledgersmb.org/mailman/listinfo/users
_______________________________________________ users mailing listusers@lists.ledgersmb.orghttps://lists.ledgersmb.org/mailman/listinfo/users
_______________________________________________ users mailing listusers@lists.ledgersmb.orghttps://lists.ledgersmb.org/mailman/listinfo/users
_______________________________________________ users mailing list users@lists.ledgersmb.org https://lists.ledgersmb.org/mailman/listinfo/users
On Sun, Mar 24, 2019 at 10:27 AM Gnucash Xboxboy Mageia <xboxboy.mageia+gnucash@gmail.com> wrote:
On Thu, Mar 21, 2019 at 11:00 PM bill Ott <billott@theotts.org> wrote:
Have you tried temporarily turning off SELinux ("setenforce 0"), then trying to connect? After doing the test, turn SELinux back on with "setenforce 1".
Thanks Just tried that on the host OS with no change. The debian VM doesn't have SElinux installed, as 'getenforce' and 'sestatus' return command not found.
I'm not sure which version of Debian you're running? Or which version of LSMB you're testing... (v1.5.x?) Have you already checked that LSMB is running and which IP & port that LSMB is being run on? I usually use 'netstat -tnlp' to verify that (part of the net-tools pkg in Debian/Ubuntu/etc, in case you didn't know...). Trying to access it via the port you mentioned seems to indicate that you're running LSMB 1.5 or LSMB 1.6 but that is defaulted to putting it up on localhost. For instance; I have the v1.5.24 version of the ledgersmb-1.5 pkg (from the apt.ledgersmb.org pkg repo) installed in a Debian v9.6 container (I use LXC) on my laptop, which I used to do a quick test of that pkg version before I made it generally available. There 'starman' (which is running LSMB) is showing like this: root@lsmbtest:~# netstat -tnlp|grep 5762 tcp 0 0 127.0.0.1:5762 0.0.0.0:* LISTEN 99/starman master - tcp6 0 0 ::1:5762 :::* LISTEN 99/starman master - Since I didn't feel like changing it to the network IP in the systemd unit (although that is doable, it gets changed back if the pkg is updated), I just used the varnish proxy (in this case, installed & configured using the ledgersmb-varnish pkg)., which made it available on the network IP up on port 6081. That shows like this: root@lsmbtest:~# netstat -tnlp|grep 6081 tcp 0 0 0.0.0.0:6081 0.0.0.0:* LISTEN 58/varnishd tcp6 0 0 :::6081 :::* LISTEN 58/varnishd -- Robert J. Clay rjclay@gmail.com jame@rocasa.us
On Mon, Mar 25, 2019 at 4:20 AM Robert J. Clay <rjclay@gmail.com> wrote:
On Thu, Mar 21, 2019 at 11:00 PM bill Ott <billott@theotts.org> wrote:
Have you tried temporarily turning off SELinux ("setenforce 0"), then
On Sun, Mar 24, 2019 at 10:27 AM Gnucash Xboxboy Mageia <xboxboy.mageia+gnucash@gmail.com> wrote: trying to connect? After doing the test, turn SELinux back on with "setenforce 1".
Thanks Just tried that on the host OS with no change. The debian VM doesn't have SElinux installed, as 'getenforce' and
'sestatus' return command not found.
I'm not sure which version of Debian you're running? Or which version of LSMB you're testing... (v1.5.x?)
Hi Robert, I'm using the apt repo, and followed the instructions: https://apt.ledgersmb.org/index.html
Have you already checked that LSMB is running and which IP & port that LSMB is being run on? I usually use 'netstat -tnlp' to verify that (part of the net-tools pkg in Debian/Ubuntu/etc, in case you didn't know...). Trying to access it via the port you mentioned seems to indicate that you're running LSMB 1.5 or LSMB 1.6 but that is defaulted to putting it up on localhost.
For instance; I have the v1.5.24 version of the ledgersmb-1.5 pkg (from the apt.ledgersmb.org pkg repo) installed in a Debian v9.6 container (I use LXC) on my laptop, which I used to do a quick test of that pkg version before I made it generally available. There 'starman' (which is running LSMB) is showing like this:
root@lsmbtest:~# netstat -tnlp|grep 5762 tcp 0 0 127.0.0.1:5762 0.0.0.0:* LISTEN 99/starman master - tcp6 0 0 ::1:5762 :::* LISTEN 99/starman master -
tcp 0 127.0.0.1:5762 0.0.0.0:* LISTEN 328/starman master tcp6 0 0 ::1:5762 :::* LISTEN 328/starman master
Since I didn't feel like changing it to the network IP in the systemd unit (although that is doable, it gets changed back if the pkg is updated), I just used the varnish proxy (in this case, installed & configured using the ledgersmb-varnish pkg)., which made it available on the network IP up on port 6081. That shows like this:
I'm sorry, I don't follow this section: Proxy's are all new to me.
root@lsmbtest:~# netstat -tnlp|grep 6081 tcp 0 0 0.0.0.0:6081 0.0.0.0:* LISTEN 58/varnishd tcp6 0 0 :::6081 :::* LISTEN 58/varnishd
-- Robert J. Clay rjclay@gmail.com jame@rocasa.us
On Sun, Mar 24, 2019 at 8:02 PM Gnucash Xboxboy Mageia <xboxboy.mageia+gnucash@gmail.com> wrote:
On Mon, Mar 25, 2019 at 4:20 AM Robert J. Clay <rjclay@gmail.com> wrote:
On Sun, Mar 24, 2019 at 10:27 AM Gnucash Xboxboy Mageia <xboxboy.mageia+gnucash@gmail.com> wrote:
.> I'm not sure which version of Debian you're running? Or which
version of LSMB you're testing... (v1.5.x?)
Hi Robert, I'm using the apt repo, and followed the instructions: https://apt.ledgersmb.org/index.html
For instance; I have the v1.5.24 version of the ledgersmb-1.5 pkg (from the apt.ledgersmb.org pkg repo) installed in a Debian v9.6 container (I use LXC) on my laptop, which I used to do a quick test of that pkg version before I made it generally available. There 'starman' (which is running LSMB) is showing like this:
root@lsmbtest:~# netstat -tnlp|grep 5762 tcp 0 0 127.0.0.1:5762 0.0.0.0:* LISTEN 99/starman master - tcp6 0 0 ::1:5762 :::* LISTEN 99/starman master -
tcp 0 127.0.0.1:5762 0.0.0.0:* LISTEN 328/starman master tcp6 0 0 ::1:5762 :::* LISTEN 328/starman master
Very good; that indeed indicates that the LSMB application itself is available where it is supposed to be.
Since I didn't feel like changing it to the network IP in the systemd unit (although that is doable, it gets changed back if the pkg is updated), I just used the varnish proxy (in this case, installed & configured using the ledgersmb-varnish pkg)., which made it available on the network IP up on port 6081. That shows like this:
I'm sorry, I don't follow this section: Proxy's are all new to me.
In our case, we use a reverse proxy, where another web application listens for http requests from a users browser (usually on the standard http ports), sends them to the LSMB application, then sends what LMSB returns back to the users browser. One can use, for instance; apache, nginx, or lighttpd as the web proxy as we support all three; emphasizing https connections for it of course. I understand that you have apache already installed? .Then installing the 'ledgersmb-1.5-apache' pkg would be useful to you; that attempts to auto configure apache to be uses as a web proxy for LSMB. Including to https connections but you'll to update the config specifically for 'ServerName'.apache config item. (In /etc/apache2/sites-available/ledgersmb-1.5-proxy.conf.) -- Robert J. Clay rjclay@gmail.com
On Wed, Mar 27, 2019 at 1:59 AM Robert J. Clay <rjclay@gmail.com> wrote:
For instance; I have the v1.5.24 version of the ledgersmb-1.5 pkg (from the apt.ledgersmb.org pkg repo) installed in a Debian v9.6 container (I use LXC) on my laptop, which I used to do a quick test of that pkg version before I made it generally available. There 'starman' (which is running LSMB) is showing like this:
root@lsmbtest:~# netstat -tnlp|grep 5762 tcp 0 0 127.0.0.1:5762 0.0.0.0:* LISTEN 99/starman master - tcp6 0 0 ::1:5762 :::* LISTEN 99/starman master -
tcp 0 127.0.0.1:5762 0.0.0.0:* LISTEN 328/starman master tcp6 0 0 ::1:5762 :::* LISTEN 328/starman master
Very good; that indeed indicates that the LSMB application itself is available where it is supposed to be.
Thanks for the reply. Ok, so that's good that it's installed and behaving so far.
Since I didn't feel like changing it to the network IP in the systemd unit (although that is doable, it gets changed back if the pkg is updated), I just used the varnish proxy (in this case, installed & configured using the ledgersmb-varnish pkg)., which made it available on the network IP up on port 6081. That shows like this:
I'm sorry, I don't follow this section: Proxy's are all new to me.
In our case, we use a reverse proxy, where another web application listens for http requests from a users browser (usually on the standard http ports), sends them to the LSMB application, then sends what LMSB returns back to the users browser. One can use, for instance; apache, nginx, or lighttpd as the web proxy as we support all three; emphasizing https connections for it of course. I understand that you have apache already installed? .Then installing the 'ledgersmb-1.5-apache' pkg would be useful to you; that attempts to auto configure apache to be uses as a web proxy for LSMB. Including to https connections but you'll to update the config specifically for 'ServerName'.apache config item. (In /etc/apache2/sites-available/ledgersmb-1.5-proxy.conf.)
Would you like me to install ledgersmb-1.5-apache? My understanding is we
then have to configure it?
-- Robert J. Clay rjclay@gmail.com
On Fri, Mar 29, 2019 at 10:53 PM Gnucash Xboxboy Mageia <xboxboy.mageia+gnucash@gmail.com> wrote:
I understand that you have apache already installed? .Then installing the 'ledgersmb-1.5-apache' pkg would be useful to you; that attempts to auto configure apache to be uses as a web proxy for LSMB. Including to https connections but you'll to update the config specifically for 'ServerName'.apache config item. (In /etc/apache2/sites-available/ledgersmb-1.5-proxy.conf.)
Would you like me to install ledgersmb-1.5-apache?
If you still plan to use Apache as the proxy (for which, access I understand was already working?), then yes.
My understanding is we then have to configure it?
As I noted above ( & allude to in the pkg README.Debian file), yes. And then the config file needs to be enabled so that apache can see it and then apache needs to be restarted in order to use the changes. -- Robert J. Clay rjclay@gmail.com
On Thu, Apr 4, 2019 at 1:40 AM Robert J. Clay <rjclay@gmail.com> wrote:
If you still plan to use Apache as the proxy (for which, access I understand was already working?), then yes.
My understanding is we then have to configure it?
As I noted above ( & allude to in the pkg README.Debian file), yes. And then the config file needs to be enabled so that apache can see it and then apache needs to be restarted in order to use the changes.
-- Robert J. Clay rjclay@gmail.com
Thank Robert, I've now installed ledgersmb-1.5-apache, I'm sorry but this reverse proxy stuff is all new to me. Where can I find this README.debian file? I think I'm going to need a walkthough to finalize this :-/
On Fri, Apr 19, 2019 at 1:03 AM Xboxboy Mageia <xboxboy.mageia@gmail.com> wrote:
Thank Robert, I've now installed ledgersmb-1.5-apache, I'm sorry but this reverse proxy stuff is all new to me.
Don't worry, it's fairly easy to pick up.
Where can I find this README.debian file?
Like for all Debian packages, it's in a directory in /usr/share/doc/ named after the package. So in this case, it's in /usr/share/doc/ledgersmb-1.5/. Note also that it's also standard on Debian that if the file is over a certain size, the file is installed as compressed; so the file name to be looked for is 'README.Debian.gz'. (I use the 'mc' app to view such files; it can handle compressed text files with no issue.) Reviewing that README file again in light of explaining it to you, I don't think I go into enough detail, so I'll need to work on that...
I think I'm going to need a walkthough to finalize this :-/
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: a2ensite ledgersmb-1.5-proxy.conf 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...) Then go to the 'DB admin login' dropdown and select "lsmb-dbadmin"; then enter its password (which would have been configured during the main pkg install). Then enter the company name you want to use in the 'Database' field. Then click on the 'Create' button. If there are no issues, the next thing that will come up after a few moments is a 'Country Code' dropdown. Select what you want to use for this company database and then click on 'Next'. The next page that comes up has dropdowns for 'Chart of Accounts' and 'GIFI'. If you want something besides the defaults there, select what you want & then click on 'Next' again. Then you get the page where you can select the Template to load. Selecting the default 'demo_with_images' is fine and you can then click on the 'Load Templates' button. The next page that comes up is for creating a user for within the LSMB application itself. For the first user being added, I'll usually set the 'Assign Permissions' dropdown to "Full Permissions". Then click on the 'Create User' button. If everything is good, you'll get one last page. It'll list the Database Credentials used to create it. And note that the 'Database Operation Complete'. And you'll have the options to 'Return to Setup', or 'Start Using LedgerSMB'. if you go to the LSMB login page, you'll need to enter the LSMB User Name (like what you just created) and its password, the Company datebase name you want to use (like what you just created). Clicking the 'Login' button should take you to the Welcome screen. Note that when you first log in with newly created user to LSMB, you might should go to the 'Preferences' pages and reset its password to ensure that it doens't expire overnight. Any questions/comments/concerns etc, please let us know. -- Robert J. Clay rjclay@gmail.com
participants (4)
-
bill Ott -
Gnucash Xboxboy Mageia -
Robert J. Clay -
Xboxboy Mageia