Local GoTrue signs JWTs with HS256, but the JWKS endpoint returns an empty key set since there are no RSA keys. Fall back to HS256 shared secret verification when JWKS fails, using SUPABASE_JWT_SECRET. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
16 lines
447 B
Plaintext
16 lines
447 B
Plaintext
# Application settings
|
|
APP_NAME="Another Nuzlocke Tracker API"
|
|
DEBUG=true
|
|
|
|
# API settings
|
|
API_V1_PREFIX="/api/v1"
|
|
|
|
# Database settings
|
|
DATABASE_URL="sqlite:///./nuzlocke.db"
|
|
|
|
# Supabase Auth (JWKS used for JWT verification)
|
|
SUPABASE_URL=https://your-project.supabase.co
|
|
SUPABASE_ANON_KEY=your-anon-key
|
|
# HS256 fallback for local GoTrue (not needed for Supabase Cloud):
|
|
# SUPABASE_JWT_SECRET=super-secret-jwt-token-with-at-least-32-characters-long
|