# A more complete docker-compose file

**URL:** <https://forum.communityhealthtoolkit.org/t/a-more-complete-docker-compose-file/1658>\
**Category:** Product\
**Tags:** configuration, deployment, onboardind\
**Created:** [January 13, 2022, 3:31pm UTC](https://forum.communityhealthtoolkit.org/t/a-more-complete-docker-compose-file/1658 "2022-01-13T15:31:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gilbert](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/gilbert/32/1325_2.png) [@Gilbert](https://forum.communityhealthtoolkit.org/u/Gilbert)\
**Post date:** [January 13, 2022, 3:31pm UTC](https://forum.communityhealthtoolkit.org/t/a-more-complete-docker-compose-file/1658/1 "2022-01-13T15:31:26Z")

</div>

Hi community,  
I just installed CHT using the docker-compose file I got learning CHT.  
I realized that only 2 containers were created (haproxy and medic-os). Is it possible to include chouch2pg and postgres db service or even sentinel to allow beginners like me to have a very good overview of a production server?  
Thanks

---

<div class="post-metadata">

**Author:** ![jkuester](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/jkuester/32/806_2.png) [@jkuester](https://forum.communityhealthtoolkit.org/u/jkuester)\
**Post date:** [January 13, 2022, 5:40pm UTC](https://forum.communityhealthtoolkit.org/t/a-more-complete-docker-compose-file/1658/2 "2022-01-13T17:40:01Z")

</div>

Hello @Gilbert! Couple of thoughts here. First of all, I think you should have Sentinel running already by default as a part of the CHT deployment in the `medic-os` container (though I am not positive if there is additional configuration needed to get it functioning…).

For `couch2pg` and `postgres`, there is some helpful documentation out on the [cht-couch2pg repo](https://github.com/medic/cht-couch2pg#running--the-docker-image) including some sample docker-compose configuration for spinning up containers for those applications and connecting them to CouchDB (although, remember that you will want to connect them with the CouchDB instance running in your `medic-os` container and not a separate `couchdb:2.3.1` container as shown in the example).

It is probably worth noting that in a typical “production” environment these containers do not have to be run on the same host server. In fact, it is probably fair to say that `postgres` is most commonly deployed on a host provisioned separately from `medic-os`.