There is another installation issue I ran into that I also wanted to document. Not sure if this should be it’s own talk post, but I’ll add it here.
Basically, if I try to do a default install (eg. nothing in deployment-artifacts) but a custom “inventory” file to limit my install to just EMR, and with no custom setup.yml, running
Hi Mike,
The “bahmni” command line utility version given for endtb release is a shell script.
The next version of that utility is a python script which is more advanced and can become an one-stop-shop for sysadmins to manage things on the environment like backups, restores, mysql & pgsql replication checks etc. This is more cutting edge and the usage you saw in the documentation is for the latest one. For now, this is still experimental.
I have updated the documentation to use the shell script version of “bahmni” utility for now. Once, the development of the python script is complete, we will update the documentation. Sorry for the confusion.
Regarding your second question, the default rpm repo configured with the bahmni installation is this. So, if the artifact is still not released officially, then the RPMs will not be available here. So, we have to override it with a nightly repo which you pointed out in the talk. So, ideally, once the current release of bahmni is out (within next few days), then you need not have to do that thing in setup.yml.