Purpose of bahmni-config container

I have a random question, I have been looking into how to set up bahmni-docker, and have been customizing the docker-compose.yml file quite a lot, to make it easier for me to manage.

I am wondering if anyone knows the idea behind the bahmni-config docker container? As far as I can tell, the config files are served by bahmni-web, and this bahmni-config container seems to start with a set of config files in /etc/bahmni_config which then get copied to /usr/local/bahmni_config, and this gets replaced by a mounted volume in the docker-compose.yaml file.

But so far I haven’t found if or where this container is actually used.

To answer my own question, this page says that to use your own config, you can build your own bahmni-config docker container with your configuration baked in, or for development, remove the bahmni-config service and only use a mounted config folder.

The bahmn-config service above just replaces whatever configuration you have with what it has baked in.

Hi Matthew, I hope you have gotten your response. Are there any more questions on this?

@mdg583 You are right, the config service comes with a out-of the box default config. If you are volume mounting please make sure, you comment out the bahmni-config service or even remove the service from docker-compose.

Thanks, sorry I didn’t check this thread in a while. We have paused work on setting up bahmni-docker for a while again. But I think I’ve understood the process.