5 Commits

Author SHA1 Message Date
CC Worker
2ccfb9ccd6 fix(dev): route Supabase same-origin via /__supabase proxy
Some checks failed
app-ci-deploy / test-build-deploy (push) Has been cancelled
app-dev built with --mode production was baking the PROD Supabase URL (.env)
into the bundle, so browser auth went cross-origin to supa.classroomcopilot.ai
and was CORS-blocked (and hit the wrong user store). Mirror the /__ccapi fix:
- Dockerfile: nginx /__supabase/ -> dev Supabase .94:8000 (+WS upgrade for realtime)
- supabaseClient.ts: resolve a leading-slash VITE_SUPABASE_URL against
  window.location.origin so supabase-js gets an absolute same-origin URL
- docker-compose.dev.yml: bake VITE_SUPABASE_URL=/__supabase (like VITE_API_BASE)
Browser now talks only to the app host (Tailscale or LAN), no CORS, dev .94 store.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-07 21:20:57 +00:00
7db852aaff [verified] route app-dev API through same-origin proxy 2026-06-07 20:43:20 +01:00
7326b9f3be [verified] fix app-dev api proxy and build env 2026-06-07 20:20:42 +01:00
0db53bfd9c test: add admin route guard coverage
Some checks failed
app-ci-deploy / test-build-deploy (push) Has been cancelled
2026-05-27 23:24:26 +01:00
e68eef8865 chore: consolidate app compose dev and prod 2026-05-27 22:55:00 +01:00