Deploy
Milestone 1 ships as a Docker image that serves the capture app. Where the container runs is chosen at runtime.
No FastAPI and no Woo client in this milestone.
docker-compose.yml, Caddyfile.fragment, and .env.example describe an older two-service stack. They are not the Milestone 1 contract.
Milestone 1 UAT — deployment POR
- One container. Build a single Docker image that serves the SvelteKit capture app. No FastAPI, no Woo client, no Caddy TLS edge in M1. (Caddy/compose/Woo are Milestone 3.)
- Host chosen at runtime. Record the machine and URL in
INVENTORY.mdwhen the container starts. Do not put a host name in the product spec. - LAN-reachable UAT URL. For UAT the container binds a port on the LAN interface (not only
127.0.0.1), so other machines on the LAN — e.g. a phone — reach the app athttp://<host-lan-ip>:<port>. - No backend. The app is browser-only in M1 (see
docs/CAPTURE.md). There is no/apiroute and no inference.
Reference for the current UAT host: see INVENTORY.md (filled in when the container starts).