Files
provenance/deploy/Caddyfile
T
justin fccc81a6cc Wire the frontend into the deploy stack and CI
Compose gains a frontend service; Caddy now routes / to frontend:3000 (keeping /api/* and /health* on the backend). CI builds and pushes a frontend image alongside the backend. Verified end-to-end on the deploy target: / serves the app, /api and /health still resolve through Caddy.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Justin Paul <justin@jpaul.me>
2026-06-06 11:03:07 -04:00

23 lines
605 B
Caddyfile

# Provenance edge. Site address is env-driven: ':80' for local http://localhost,
# a domain in production for automatic HTTPS. Behind a Cloudflare Tunnel you can
# keep this on plain HTTP and let the tunnel terminate TLS.
{$PROVENANCE_SITE_ADDRESS::80} {
encode gzip
# Versioned API surface (FastAPI). The assistant mounts under /assistant later.
handle /api/* {
reverse_proxy backend:8000
}
# Liveness/readiness probes, proxied for external monitoring.
handle /health* {
reverse_proxy backend:8000
}
# Everything else -> the Next.js frontend.
handle {
reverse_proxy frontend:3000
}
}