The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:
Changelog for 1.8.24
* Fix multiple issues with bank account reconciliation (#6122)
* Fix correct AR/AP account being selected on Update and when editing (#6191)
* Fix the end date on credit accounts being shown correctly (#6235)
* Fix calculation of credit limit remaining shown on transactions and invoices
* Fix credit limit remaining calculation for foreign currency transactions
* Fix login errors being hidden behind an "insecure response" error (#6251)
* Fix GL batch import menu item missing, even with appropriate permissions (#6248)
For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.8.24/README.md
The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.8.24
The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.8.24
Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.8.24
These are the sha256 checksums of the uploaded files:
9fa485960be1a0c7500e60d2041380d494c84b542706e4fba3150b4c43657275 ledgersmb-1.8.24.tar.gz
1aafc72d4fe1ca161b6a0c3bbc00d299e4f1fb621774c37330d671493d528b16 ledgersmb-1.8.24.tar.gz.asc
The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:
Changelog for 1.7.37
* Fix login errors being hidden behind an "insecure response" error (#6251)
For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.7.37/README.md
The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.7.37
The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.37
Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.7.37
These are the sha256 checksums of the uploaded files:
4508200782fd5f39b4ac14521c80e0112f224c8db50581e2829e686c7555a82d ledgersmb-1.7.37.tar.gz
db63bf9c2c3c3cfcf0ca87fbb2aa835a8c28322ee2f48d522fbbdb1a2e500624 ledgersmb-1.7.37.tar.gz.asc
Hi Johann,
On Wed, Dec 8, 2021 at 8:50 AM <greyling(a)ruens.co.za> wrote:
> I am experiencing problems during the initial setup of LedgerSMB using
> your docker image and a pulled postgres image.
> I include the commands issued when running these images on user defined
> bridge for evaluation purposes. Am using UBUNTU 18
> The problem seems to be an authentication error for the postgres user.
> Any guidance will be welcomed
>
May I suggest you use the accompanying "docker-compose" file, which sets up
a network bridge and two (linked) containers out of the box? There seems to
be a problem for one container reaching the other. (I'm not quite clear on
why this would be the case.)
If you have Docker installed, installing docker-compose is trivial (
https://docs.docker.com/compose/install/#install-compose-on-linux-systems)
and using it with the LedgerSMB docker images is really simple:
https://github.com/ledgersmb/ledgersmb-docker#docker-compose-installation-a…
Regards,
Erik.
-- Preview attachment LedgerSMB.pdf
LedgerSMB.pdf
30 KB
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
Hello again!
I found a nice Black Friday special on a server I can afford.
So, another time, 4th time, but who's counting?
As I suspected, I would hit a moment where I couldn't come up with $136
a month. So I had to drop that server. Same server, but $67 now.
I saved my work on github, which is a big mess, but will help a lot.
I learned a ton about submitting and how to deal with that set of Locale::CLDR
modules.
I also had a strange problem. As far as I have seen, nobody has ever
done a project with dozens of dependencies to bring in as just a single
person. These types of projects have always been done by groups or
really top notch porters, with commit powers to the CVS repository.
One problem I had was not seeing the obvious solution to how to deal
with really long chains of new dependencies.
The people who review submissions DO NOT want single ports to be
submitted one at a time, because they are very busy.
It didn't occur to me how to deal with this problem until after I
stopped working on this.
Rather than submit a ridiculously long set of 12 or more dependencies
from the LedgerSMB cpanfile outwards, I needed to go out to the end of
the chain and work inwards instead, thus submitting only 2-4 at a time.
I am now starting up again.
I would really appreciate any help, including just a little bit.
Even getting just one Perl module ready to submit is more than enough.
Different OS's have different goals. OpenBSD is primarily security
oriented, so the method of getting a port ready is very strict.
Building a port outside of the porting system is strictly forbidden.
The FAQ's about porting and the man pages are a bit overwhelming, but
most of the needed dependencies are pretty easy to work with.
It does require running OpenBSD -current, but that has been amazingly
good for quite some time.
If you would either like to help or just tell me if you are wanting this
to be done, please let me know. Just telling me you want this is really
encouraging for me.
My ugly mess is at https://github.com/CPBen/LSMB-for-OBSD-WIP
It's so messy since I had to upload and download a few hundred GB to and
from home and across two servers. Sorry.
--
Regards,
Chris Bennett
