Files
app/docker/compose.lan.yml
T
Melvin StroblandClaude Opus 5.5 0c7f8bde82
Docs / docs (push) Successful in 22s
Playwright Tests / test-playwright (1, 2) (push) Failing after 2m51s
Playwright Tests / test-playwright (2, 2) (push) Successful in 2m5s
pre-commit / pre-commit (push) Failing after 2m24s
Test Backend / test-backend (3.12) (push) Successful in 4m9s
Test Backend / test-backend (3.14) (push) Successful in 4m14s
Compose Smoke Test / test-compose (push) Successful in 32s
Playwright Tests / merge-reports (push) Successful in 1m45s
LAN stack gives out its LAN address: dev-lan sets FRONTEND_HOST to the published port on the host's default-route address, so the Panels dialog links a screen somewhere it can reach instead of app.localhost
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016ezWcLmBCtTVKFPxfdK2MK
2026-10-15 22:22:58 +02:00

28 lines
1.1 KiB
YAML

# Direct LAN access — layered on top of compose.local.yml by `make dev-lan`.
#
# For reaching the app from a machine that cannot be given a DNS record or a
# hosts entry. Traefik routes on the Host header and a bare IP matches no
# router, so the frontend is published on a host port instead and proxies the
# API and the hooks on that same port: http://<host-ip>:${APP_PORT} is the
# whole app.
services:
backend:
environment:
# The address the instance gives out: the link the Panels dialog shows a
# screen and the one its emails carry. app.${DOMAIN} resolves on this host
# only, so `make dev-lan` passes the published port on the LAN address.
- FRONTEND_HOST=${LAN_URL:-http://app.${DOMAIN:-localhost}}
frontend:
ports: !override
- "${APP_PORT:-8080}:80"
volumes:
- ./nginx-api-proxy.conf:/etc/nginx/extra-conf.d/backend-not-found.conf:ro
build:
args:
# Empty on purpose: the client then addresses the API as a path on
# whichever origin served the page, so one build works through
# app.${DOMAIN}, the published port, and an ssh tunnel alike.
- VITE_API_URL=