Recently some of the python/rpm packages on which Bahmni installation depends are no longer available in the mentioned links (on the installation page). So, some custom commands have to be fired. I think the install steps need a re-write due to this.
I see the following options for now:
- V0.93 of Bahmni will be out soon. In about 2 weeks. Wait for that, and follow the install steps mentioned with the V0.93 release.
- Dockerisation of Bahmni is in progress. With docker, all you need to install on the machine is “docker” + docker-compose. After that all installation happens using docker images (which are like mini-VMs running as processes on the host OS). Since all packages and softwares are pre-baked into these docker images by us, one doesn’t need to install anything – just start/stop the container running these images. You can see the documentation on docker for Bahmni here: bahmni-package/bahmni-docker at master · Bahmni/bahmni-package · GitHub. Here Odoo, ELIS and OpenMRS are already dockerised. Next steps are to dockerize EMR UI, Dcm4chee, etc. You can try these out, and point your local EMR UI to point to dockerized OpenMRS backend. See instructions. We will create a video for this too soon.
- Continue with the V0.92 install process, debug the issues as they arise – and see the talk forum for specific answers and move ahead. Admittedly, I find this option painful. I would rather have one bash script that I run on CentOS – and that should just DO IT ALL for me.
- You can also try and run Vagrant on DigitalOcean (V0.92). That should also be fine for now. There are some installations in production that run on Vagrant (although this will be the first one to install Bahmni Vagrant on Cloud in my opinion).
Docker is the way to go in the future. It removes all the worries about packages/dependencies no longer being available in 3rd party repositories. And docker images are pre-created by us, and therefore pre-tested/pre-secured to a degree.