server: docker: fix traefik not being able to discover server

tl;dr: Since the server is in both the postgres instance's isolated
"backend" network and the public-facing "docker-net", traefik
unfortunately happened to decide to use the "backend" network for its
proxying purposes. This led to the server not being reachable at all.

This commit fixes that by explicitly telling traefik which network to
use.

Signed-off-by: Max R. Carrara <max@aequito.sh>
This commit is contained in:
Max R. Carrara 2025-08-16 22:52:06 +02:00
parent 68e7a9720a
commit 9d1a61885c

View file

@ -62,6 +62,7 @@ services:
- "traefik.http.routers.wien-talks-web.entrypoints=secure"
- "traefik.http.routers.wien-talks-web.service=wien-talks-web-service"
- "traefik.http.services.wien-talks-web-service.loadbalancer.server.port=${SERVERPOD_WEB_SERVER_PORT}"
- "traefik.docker.network=docker-net"
volumes:
db: