Attach frontend to external coolify network so Traefik can route

Coolify's Traefik defaults to the 'coolify' network, but the frontend was only on the per-resource network -> Traefik couldn't reach it (000/empty reply). Join the external coolify network + set traefik.docker.network=coolify.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
2026-06-12 11:31:25 +02:00
parent 8653ce2cc5
commit 68549637d7

View File

@@ -29,6 +29,8 @@ services:
# Persist the SQLite file across container rebuilds.
- visigine_data:/data
restart: unless-stopped
networks:
- default
frontend:
build:
@@ -41,6 +43,18 @@ services:
backend:
condition: service_healthy
restart: unless-stopped
# Join Coolify's proxy network so Traefik (which defaults to the `coolify`
# network) can reach this container, and point Traefik at that network
# explicitly since the container is attached to several.
networks:
- default
- coolify
labels:
- "traefik.docker.network=coolify"
networks:
coolify:
external: true
volumes:
visigine_data: