Hi there! I’m trying to run the local set up of CHT Sync per the docs . My assumption is that the values in env.template file are valid as is for a happy path of running the full stack - but maybe this is not the case? My steps so far have been: clone the repo locally copy the env.template to .en…

oh - update! the next section in the docs “ Separate CouchDB instance ” seems to work well! Here’s the steps I took for this: set up a docker helper instance at https://192-168-68-26.local-ip.medicmobile.org:10445/ edit my .env bottom #coucdb section to be:# couchdb COUCHDB_USER=medic COUCHDB_PASS…

@njuguna tracked the issue down to the medic database not existing in couch and created an issue to track the fix for it.

@mrjones an update on this. After some discussion we decided that running CouchDB as part of the CHT Sync setup is not very beneficial. Connecting to an existing CouchDB instance has the added benefit that users can see they sync process as they add docs to their CouchDB instance rather than having …

Gotcha - makes sense! I agree - given most folks will want to see their data from the CHT Core instance. Thanks for the followup!

Community Health Toolkit

Running local CHT Sync setup with couch2pg, PostgreSQL, pgAdmin, dbt, and CouchDB

Technical Support