Just pondering over customization of the Standalone for particular users where there is limited IT capacity and support. Is there any simple way of re-packaging the Standalone after customizing it - such as add customized forms and reports and then re-package it for distribution?
In other words, how complex is the process of packaging the Standalone and can this be shared with Developers interested in producing customized Distros of OpenMRS?
The simplest way is to just add your forms, reports, etc to a standalone instance and just zip it again for distribution. The end users will just unzip and run.
That sound cool. Will give it a try to see.
The approach being used within Uganda for distribution is:
Build a custom module that contains the forms and reports
For the openmrs-distro-platform project and customize it to include the custom module above, and any dependent modules via the pom.xml file to build a WAR file for your distribution
This is fascinating.
Has the experience of Uganda with developing and deploying Customized
Distros of OpenMRS been documented and shared before?
If so, can you send me a copy or the link to it. It would be nice to
know what motivated it and what has been the success (and challenges)
of its deployment.
If not, can you spare some time to do so in not too many pages.
The Github repo for the distro is https://github.com/METS-Programme/openmrs-distro-platform-uganda. The reason for this is to ensure that there is a consistent package to distribute to the over 1,000 installation expected to occur in the next 1 year.
The customization made is the modules folder where modules that cannot be accessed via the pom file are placed. This may include custom builds (ahead of official releases), although the idea is to use as few of these as possible.
A writeup is in the offing but not yet concrete, but happy to answer questions