Upgrading Bahmni on CentOS to Bahmni Standard on Docker

Software Bahmni
, , , ,
1

The documentation for upgrading Bahmni on CentOS to Bahmni Standard on Docker is very fragmented and confusing for beginners. I followed this documentation (Using Implementation specific Configuration (docker)) and this one (Upgrading Bahmni on CentOS to Bahmni Standard (or Lite) on Docker), but still I can’t get everything working the way I want it to. I was also following this video ([DAY 2] 2.1 Using Implementation Specific Config).These are the issues I am currently facing:

  1. I want to change the title on the landing page to indicate that its DEV instance, but my changes are not reflecting
  2. In this document, under Starting EMR Components, it says:

Wait for the containers to boot up, run the required migrations.

but I don’t know which migrations the comment is referring to because I thought the restore script is supposed to restore everything.

I can’t even update the logo because when I inspect it, it’s referencing the /bahmni/images/ directory which was not backed up when I ran cp -a /opt/bahmni-web/etc/bahmni_config /bahmni-backup/ as per this documentation. In Centos, the logo is in this directory /opt/bahmni-web/etc/bahmniapps/, but there’s nowhere in the documentation where it says it should be backed up.

Please I desperately need help with this, I have to have migrated to Docker, including production by March 7th

@dkayiwa @angshuonline @mohant

2

If the white labelling changes are not reflected, it is likely due to your custom configuration not mounted properly. Try to hit /bahmni_config/openmrs/apps/home/whiteLabel.json URL on your browser to verify if the updated JSON is returned.

3

I was able to figure out what the issue was, I had used a relative path in the CONFIG_VOLUME variable, after I used an absolute path everything worked.