Remove custom network so Coolify/Traefik can route (fixes empty HTTPS reply)
Frontend was on two networks; Traefik (on only one) couldn't reach it -> 000/empty reply on HTTPS while nginx served 200 directly. Letting Coolify manage networking puts both services on its single proxy network; service-name DNS (backend) still resolves. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -29,8 +29,6 @@ services:
|
|||||||
# Persist the SQLite file across container rebuilds.
|
# Persist the SQLite file across container rebuilds.
|
||||||
- visigine_data:/data
|
- visigine_data:/data
|
||||||
restart: unless-stopped
|
restart: unless-stopped
|
||||||
networks:
|
|
||||||
- visigine
|
|
||||||
|
|
||||||
frontend:
|
frontend:
|
||||||
build:
|
build:
|
||||||
@@ -43,12 +41,6 @@ services:
|
|||||||
backend:
|
backend:
|
||||||
condition: service_healthy
|
condition: service_healthy
|
||||||
restart: unless-stopped
|
restart: unless-stopped
|
||||||
networks:
|
|
||||||
- visigine
|
|
||||||
|
|
||||||
networks:
|
|
||||||
visigine:
|
|
||||||
driver: bridge
|
|
||||||
|
|
||||||
volumes:
|
volumes:
|
||||||
visigine_data:
|
visigine_data:
|
||||||
|
|||||||
Reference in New Issue
Block a user