feat(app): optional Supabase connection in runtime config + lazy typed client
- env.ts: supabase: SupabaseConnection | null resolved from env.js (supabaseUrl/supabaseAnonKey), VITE_SUPABASE_*, else null; half config refused - lib/supabase.ts: getSupabaseClient() null when unconfigured, one client per URL - entrypoint.sh writes the two public values; .env.example placeholders - Dockerfile copies packages/supabase manifest for the install layer - no UI change; 7 new tests (278 app)
This commit is contained in:
1 parent
ce76c6597a
commit
d239374d81
9 files changed
+153
-23
No files matched your search
@@ -8,5 +8,11 @@ APP_BRAND_NAME=Osteo Report
|
||||
APP_FOOTER_NAME=Osteo Report
|
||||
APP_TAGLINE=Bilans d'ostéopathie animalière
|
||||
|
||||
# Supabase connection exposed to the browser (public values, RLS protects data).
|
||||
# Empty = app runs without backend. Local stack: `pnpm db:start` prints both.
|
||||
# NEVER put the service_role key here or in any browser-facing variable.
|
||||
APP_SUPABASE_URL=
|
||||
APP_SUPABASE_ANON_KEY=
|
||||
|
||||
# Docker Compose project namespace
|
||||
COMPOSE_PROJECT_NAME=osteo-report
|
||||
Reference in new issue
Block a user