## Summary
- Pass `SUPABASE_JWT_SECRET` to backend in `docker-compose.prod.yml` so it can verify JWTs from Supabase Cloud
- Add `ARG` lines to `Dockerfile.prod` for `VITE_API_URL`, `VITE_SUPABASE_URL`, `VITE_SUPABASE_ANON_KEY` so Vite inlines them at build time
- Pass build args from Gitea secrets in the deploy workflow
- Add `build` section to frontend service in `docker-compose.prod.yml` for local prod builds
No GoTrue container needed in prod — Supabase Cloud hosts the auth service.
## Setup required
Add these secrets to the Gitea repo (Settings → Secrets):
- `SUPABASE_JWT_SECRET` — from Supabase dashboard → Settings → API → JWT Secret
- `VITE_API_URL` — production API URL (e.g. `https://api.nuzlocke.nerdboden.de`)
- `VITE_SUPABASE_URL` — Supabase project URL (e.g. `https://xyz.supabase.co`)
- `VITE_SUPABASE_ANON_KEY` — Supabase anon/public key
Add to production `.env` on the deploy target:
- `SUPABASE_JWT_SECRET=<jwt-secret>`
Configure in Supabase dashboard → Authentication → URL Configuration:
- Site URL: production frontend URL
- Redirect URLs: `<frontend-url>/auth/callback`
🤖 Generated with [Claude Code](https://claude.com/claude-code)
- Pass SUPABASE_JWT_SECRET to backend in docker-compose.prod.yml
- Add build args (VITE_API_URL, VITE_SUPABASE_URL, VITE_SUPABASE_ANON_KEY)
to Dockerfile.prod so Vite inlines them at build time
- Pass build args from secrets in deploy workflow
- Add build section to frontend service in docker-compose.prod.yml
No GoTrue container needed in prod — Supabase Cloud hosts the auth
service. The backend only needs the JWT secret to verify tokens.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Instead of relying on a pre-existing .env file on the server, the
deploy workflow now writes POSTGRES_PASSWORD and SUPABASE_JWT_SECRET
from Gitea secrets. This keeps all secret management in one place.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
TheFurya
merged commit 7276f05dd2 into develop2026-03-21 12:19:33 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
SUPABASE_JWT_SECRETto backend indocker-compose.prod.ymlso it can verify JWTs from Supabase CloudARGlines toDockerfile.prodforVITE_API_URL,VITE_SUPABASE_URL,VITE_SUPABASE_ANON_KEYso Vite inlines them at build timebuildsection to frontend service indocker-compose.prod.ymlfor local prod buildsNo GoTrue container needed in prod — Supabase Cloud hosts the auth service.
Setup required
Add these secrets to the Gitea repo (Settings → Secrets):
SUPABASE_JWT_SECRET— from Supabase dashboard → Settings → API → JWT SecretVITE_API_URL— production API URL (e.g.https://api.nuzlocke.nerdboden.de)VITE_SUPABASE_URL— Supabase project URL (e.g.https://xyz.supabase.co)VITE_SUPABASE_ANON_KEY— Supabase anon/public keyAdd to production
.envon the deploy target:SUPABASE_JWT_SECRET=<jwt-secret>Configure in Supabase dashboard → Authentication → URL Configuration:
<frontend-url>/auth/callback🤖 Generated with Claude Code