marvin/Wizard
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Serve API and website behind Caddy path prefixes

Browse Source 
Caddy forwards /wizard/api/* and /wizard/website/* with the prefix
stripped, so the server received /ws instead of /api/ws and the website
connected to /api/ws on the domain root.

- Server routes are now /ws and /health (was /api/ws, /api/health)
- Website derives the websocket URL from its own location (../api/ws),
  giving /wizard/api/ws in production and /api/ws in development
- Vite dev proxy strips /api like the production proxy
- nginx back to the plain SPA config since Caddy strips the prefix
- /internal/ai rejects requests that came through the reverse proxy,
  in addition to the shared secret
- Docs updated for the prefixed deployment

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
marvin
2026-09-27 10:00:29 +02:00
co-authored by Claude Opus 5.5
parent 00c73306d7
commit 90176e1cca
13 changed files with 60 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files
wizard_website/README.md
+4 -3
View File
@@ -6,13 +6,14 @@ React + TypeScript frontend (Vite). All component styles are CSS modules
```bash
npm install
npm run dev # http://localhost:5173, proxies /api (incl. websocket) to localhost:8000
npm run dev # http://localhost:5173, proxies /api/* (incl. websocket) to localhost:8000 without the /api prefix
npm run build
npm run lint
```
Set `WIZARD_SERVER_URL` to proxy to another server in development, or
`VITE_WS_URL` at build time to connect to an absolute websocket URL.
The app is built with relative asset paths and connects to `../api/ws` relative to its own URL
(`/wizard/website/` → `/wizard/api/ws`). Set `WIZARD_SERVER_URL` to proxy to another server in
development, or `VITE_WS_URL` at build time to use an absolute websocket URL instead.
## Structure