Dockerised demo refapp, and other questions about demo data

[raff (Rafal Korytkowski)]

@cintiadr

So, what exactly is the plan with the generated docker compose? Would it be that people would commit that (and get it build by dockerhub or a CI)? Use it as initial Docker files to customise per distro? Can I do the same with, let’s say, with GitHub - openmrs/openmrs-distro-platform: This project is used to package the core OpenMRS war file with bundled modules ?

Also, it doesn’t have the demo data straightaway, it can generate the data.

SDK uses openmrs-distro.properties to generate docker files and fetch relevant modules/war, e.g. https://github.com/openmrs/openmrs-distro-referenceapplication/blob/master/package/src/main/resources/openmrs-distro.properties

Distros can modify such a file to include/update custom modules and then recreate docker files, which can be distributed in any way (preferably as built images in dockerhub).

The demo data needs to be generated the way @dkayiwa described with the referencedemodata module and afterwards you should do a dump and store it in a repo. You do that manually and just once.

GitHub - openmrs/openmrs-distro-platform: This project is used to package the core OpenMRS war file with bundled modules does not yet contain openmrs-distro.properties, but it should be migrated to use that.