fix: attach couchdb to coolify external network for Traefik routing
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.
This commit is contained in:
@@ -10,6 +10,9 @@ services:
|
|||||||
- "5984"
|
- "5984"
|
||||||
volumes:
|
volumes:
|
||||||
- couchdb_data:/opt/couchdb/data
|
- couchdb_data:/opt/couchdb/data
|
||||||
|
networks:
|
||||||
|
- default
|
||||||
|
- coolify
|
||||||
|
|
||||||
couchdb-init:
|
couchdb-init:
|
||||||
image: curlimages/curl:latest
|
image: curlimages/curl:latest
|
||||||
@@ -55,5 +58,9 @@ services:
|
|||||||
put_config cors methods 'GET, PUT, POST, HEAD, DELETE'
|
put_config cors methods 'GET, PUT, POST, HEAD, DELETE'
|
||||||
put_config cors headers 'accept, authorization, content-type, origin, referer, x-csrf-token'
|
put_config cors headers 'accept, authorization, content-type, origin, referer, x-csrf-token'
|
||||||
|
|
||||||
|
networks:
|
||||||
|
coolify:
|
||||||
|
external: true
|
||||||
|
|
||||||
volumes:
|
volumes:
|
||||||
couchdb_data:
|
couchdb_data:
|
||||||
|
|||||||
Reference in New Issue
Block a user