Context
PR #181 introduced VITE_API_BASE_URL as a Vite build-time env var for the frontend API client (orchestrator-ui/src/api.ts). It defaults to /api and is documented in orchestrator-ui/README.md, but it is absent from the root .env.example.
Per CLAUDE.md: "Any new env var must be added to .env.example."
Although this is a build-time var (not a Docker Compose runtime secret), adding it to .env.example as a commented reference ensures deployers know it exists when building outside the default Compose setup.
What to do
Add a commented entry to .env.example:
# Frontend build-time var — override if the API is not served at /api
# VITE_API_BASE_URL=/api
Non-blocking — the default of /api (via Vite dev proxy) works for all current local development.
Context
PR #181 introduced
VITE_API_BASE_URLas a Vite build-time env var for the frontend API client (orchestrator-ui/src/api.ts). It defaults to/apiand is documented inorchestrator-ui/README.md, but it is absent from the root.env.example.Per CLAUDE.md: "Any new env var must be added to
.env.example."Although this is a build-time var (not a Docker Compose runtime secret), adding it to
.env.exampleas a commented reference ensures deployers know it exists when building outside the default Compose setup.What to do
Add a commented entry to
.env.example:Non-blocking — the default of
/api(via Vite dev proxy) works for all current local development.