Tryton ERP/ GNU health a second look ?

[icf20]

https://www.turnkeylinux.org/forum/general/20120711/tklpatch-tryton-erp

1 is there any chance to take a second look at this?

2 what about GNU health since is based on tryton

tia

[JedMeister]

We'd be happy to look at adding an appliance for either of those to the library. But unfortunately our resources are limited and our backlog is long, so we're not currently in a position to do the work to create the appliance.

However our build tools are packaged as an appliance: "TKLDev".

If you have some understanding and experience with Linux and Bash, the I reckon you'd get the hang of how it works pretty quick.

On the web site you can find a couple of doc pages:

• Build an ISO on TKLDev - possibly a good place to start for a basic feel for TKLDev - although not directly relevant to actually building an appliance.
• Build a new appliance with TKLDev - an overview of what is needed to do and how to create a new appliance.
• Further TKLDev docs here on GitHub

Those docs are all somewhat dated, but process has changed very little over time, so they should all still be relevant. Although I think the doc on GH are probably a bit disorganised.

With regard to Tryton ERP specifically, there was actually a "TKLPatch" attached to the OP of that thread, but it was hidden. I've just edited the post to publicly include the download link (look for the line near the top that starts "TKLPatch download").

FYI "TKLPatch" was the tool that TurnKey provided for users to contribute new appliance buildcode. It has since been superseded by TKLDev - but the appliance build code uses a very similar layout to the internals of a TKLPatch archive.

I strongly suspect that some of the Tryton ERP patch code would need to be updated, but it would be a solid start. I suggest that the best way to start would go something like this:

• Download a TKLDev ISO and install - probably to a VM
• Create a new repo in your GitHub account - call it something like "tryton-erp" - or whatever you want so long as it makes sense.

Then the next steps you'll need to run from the commandline of your TKLDev.

Substituent these in the below CLI instructions:

TKL_LAPP_REPO - get this from the LAPP build code page - click the green "Code" button and copy the relevant URL
APP_NAME - What ever you want to call the appliance, can be the name of your repo ,but doesn't need to be.
YOUR_TRYTON_REPO - same as TKL_LAPP_REPO - but from your GH repo

# set up initial tryton app build dir
cd products
git clone  -o upstream TKL_LAPP_REPO  APP_NAME
cd APP_NAME
git remote add origin YOUR_TRYTON_REPO

# download, unpack and copy in tkl-patch code
cd products
wget https://www.turnkeylinux.org/files/attachments/tryton-on-lapp.tar.gz
tar xf tryton-on-lapp.tar.gz
mv tryton-on-lapp/conf APP_NAME/conf.d/tryton
mv tryton-on-lapp/overlay/* APP_NAME/overlay/
rm -r tryton-on-lapp

# commit initial code and push back to your GitHub repo
git add .
git commit -m "Initial commit of buildcode" # or whatever message you want
git push origin master

Then hack on the code until you have a working app.

If you get stuck, please ask; giving as much info as possible.

[marcos-mendez]

@icf20

I am personally a fan of GNU Health despite the legal disputes it has had with the Odoo/OCA community, of which I am a part. It is regrettable that a project aimed at public health has ego clashes over where the project is executed. Until recently, GNU Health was just a Python program that could run with Triton or Odoo.

That said, and knowing that GNU Health works within Odoo, I recommend taking a look at this fabulous ERP framework.

The big problem with GNU Health (and I say this as someone who manages public health in Brazil, where we have a public health system larger than the NHS) is that it doesn't think about the hospital from the infrastructure side, only the patient side. Therefore, those who use GNU Health need an ERP alongside it. In the end, if a patient undergoes a surgical procedure, for example, GNU Health tracks it up to the first page. We have the patient's medical records, medications, and post-procedure recommendations. However, there is a universe of operational procedures that are neither clinical nor therapeutic and are not linked to the patient (payroll for nurses, overtime, allocation of special resources, cleaning of the operating room, maintenance of operating room equipment, etc.).

I suggest you take a look at our community because there are two types of people who run Odoo and an HMS together. Those who set up Docker and struggle to reinvent the wheel and those who combine hunger with the desire to eat (after all, here in Brazil we don't have many resources, so we need scalable and low-maintenance solutions).

The TKL project has been our great ally in this story, but don't confuse it with long-term applications. I leave this as a comment because I have dealt with both universes and can tell you that if you manage health systems, you know how important quality of life is for us who maintain this infrastructure. Personally, I had serious health problems because I didn't have management that prioritized the old saying: Less is More.

I open my contact in case you want to talk, as we are few in the field and it is always good to support each other.

Best regards from Brazil.

[JedMeister]

Thanks for dropping in with your comment @marcos-mendez. You are a legend! 😁

It certainly does sound like running GNU Health within Odoo would be a good option. I'm assuming that it can be integrated with other ERP functionality of Odoo right? Sounds much better than trying to manage 2 separate systems.