516daf0b07
The container was only on the project's default network, so Coolify's Traefik (on the shared coolify network) had no route to it — Traefik matched the router but reported "no available server". Putting couchdb on both networks lets Traefik reach 5984 while leaving the init sidecar talking to it over the default network as before.
coolcouch
CouchDB 3 on Coolify. The couchdb-init sidecar waits for the server to come up, creates the three system databases, and enables CORS via the config API — no file mounts required.
Deploy
- In Coolify: New Resource → Docker Compose and point it at this repository.
- In the resource's Environment Variables tab, set:
COUCHDB_PASSWORD— requiredCOUCHDB_USER— optional, defaults toadmin
- In the resource's Domains tab, assign a domain to the
couchdbservice on port5984. Coolify fillsSERVICE_FQDN_COUCHDB_5984from this. - Deploy.
couchdb-initruns once, exits, and won't restart.
Verify
Replace $DOMAIN and $PASS:
curl -fsS https://$DOMAIN/_up
curl -fsS -u admin:$PASS https://$DOMAIN/
curl -fsS -u admin:$PASS https://$DOMAIN/_all_dbs
curl -fsS -I -X OPTIONS https://$DOMAIN/ \
-H "Origin: https://example.com" \
-H "Access-Control-Request-Method: GET"
Expected: _up returns {"status":"ok",...}; / returns the CouchDB welcome JSON; _all_dbs returns ["_global_changes","_replicator","_users"]; the preflight returns 2xx with an Access-Control-Allow-Origin header.
If the init logs show CORS errors, you can re-trigger only that step by redeploying — the PUTs against /_node/_local/_config/... are idempotent.
CORS
Wildcard origin (*) with credentials = false — the only browser-spec-legal combination with a wildcard. For credentialed auth from the browser, edit the put_config cors origins/credentials lines in docker-compose.yml.
Files
docker-compose.yml— services, volume, Traefik labels, init sidecar