Why was neso abondoned?

I’m just curios why “neso” was abandoned?! The code is about 400 lines of code so I’d assume its not too hard to maintain.

Mainly lack of interest, if I remember correctly.
Packaging was lagging behind and support was OS dependent.
Security of an ERP as a desktop application was an open topic too.

Another factor is that nowadays you can run the server on any desktop machine using the docker images for example. So there are no need of maitaining such lines of code.

Well , to add to the arguments above:

IIRC another strong reason was, that neso worked out-of-box with an sqlite database, thus with problematic/no multiuser support. And if someone after some trial with neso wanted to change to a postgresql setup this migration was not supported.

Thanks for the insights. Lack of interest is the most convincing one for me.

I’m still a bit curious about these arguments:

worked … with an sqlite database, thus with problematic/no multiuser support

AFAIK, sqlite is a full-featured DBMS. Why should it not allow multiuser?

docker images

Oh, well, getting docker to run on e.g. a Windows machine is not pracical for non-IT persons.

Sqlite does allow multiuser, but it does file locking for writes. And as the whole database is a file concurrent writes queue up.

I didn’t know this. Does it work ? and is psql → sqlite possible ?

There are tools to help with such migrations, both ways. I have no experience with any of them, I would never try to use sqlite as a Tryton production database.

I took the chance to search for conversion tools. There seem to be some.

If you wish to support non-IT people running a Tryton server locally on Windows, you might consider creating a VirtualBox “appliance” for them. Installing VirtualBox is a straight-forward procedure like any Windows application. After starting VirtualBox, the user would simply pick [File > Import Appliance] from the VirtualBox Manager window, and then use either their browser to access Tryton (if the appliance includes sao) or install and use the Windows Tryton Desktop Client.

Minor gotchas are that the host PC has to be “not old” so that it has a CPU with virtualization support and virtualization must be enabled in the BIOS/UEFI config (which may be the default on recent PCs, although I do not know if this is the case).

Creating an appliance is simple but will need a somewhat-IT person :wink: . You create a new virtual machine with minimal system configuration and appropriate port forwarding, install the OS of your choice and either a “baremetal” install of Tryton or simply install the Docker container, then stop the VM and export it as an appliance to distribute.

The same appliance may also be usable in enterprise versions of Windows (with support for virtual machines and/or WSL) and possibly also with VMWare, but I do not know for certain as I personally have only used VirtualBox for running vm’s on Windows. The last time I checked, one had to purchase a VMWare license in order to create a VM (although the VMWare “Player” was free), and I don’t have a PC new enough to run WSL.

Just a thought…