I have been running the demo version of Ozone HIS, as mentioned previously, but had to fork the repo to try to address the following issues:
- Java out-of-memory error
- The VM invariably running out of disk space within days; I first thought it was the Docker logs and changed the maximum log size (see my Docker cheatsheet), but now I think it is an issue with Zope; SENAITE the LIMS software runs on Plone the content management system, which runs on Zope the application server; Zope has a database which records every transaction, and can grow very large; once it reaches above 20Gb in my VM the system goes down.
- Superset is not working (not accessing any data).
Last night I was syncing my fork and thought it was asking me to merge in upstream changes, but I hadn’t noticed that I had somehow switched to the main developers repo and by clicking various buttons without thinking about it too much ended up submitting a pull request for some of my changes to the main repo (GitHub makes things too easy). I immediately realised what I had done and closed the pull request with an apology. I had also responded to a query on the OpenMRS forum about the issue. Luckily what I had submitted was only sensible changes to the default configuration for the Ozone HIS Docker deployment, so I got a friendly message from a couple of developers saying they would address the issue. Open source at its best. But I will be more careful with GitHub in future.