.env.example

# =============================================================================
# ABStrack — environment templates (safe to commit; no real secrets)
# =============================================================================
#
# This monorepo has three apps. Each has its own env template next to the app.
# Do not copy this root file into an app — it has no variables.
#
# | App                         | Template                              | Create locally                    |
# |-----------------------------|---------------------------------------|-----------------------------------|
# | User web (Next.js)          | apps/web/.env.example                 | apps/web/.env.local               |
# | Practitioner web (Next.js)  | apps/practitioner/.env.example        | apps/practitioner/.env.local      |
# | Mobile (Expo / Metro)       | apps/mobile/.env.example              | apps/mobile/.env                  |
#
# From the repository root:
#
#   cp apps/web/.env.example apps/web/.env.local
#   cp apps/practitioner/.env.example apps/practitioner/.env.local
#   cp apps/mobile/.env.example apps/mobile/.env
#
# Then fill in real values in each file. Full walkthrough: docs/DEV_SETUP.md
#
# Supabase project (dev / staging)
# --------------------------------
# 1. Create a project: https://supabase.com/dashboard
# 2. Authentication → Providers → enable Email (email + password), per PRD §1.
# 3. Keys: Settings → API Keys (or Connect dialog).
#    Publishable (`sb_publishable_…`) for browser/mobile clients.
#    Secret (`sb_secret_…`) for server-only @abstrack/supabase/admin.
#    https://supabase.com/docs/guides/api/api-keys
#
# This repo does not use legacy JWT anon env vars or SUPABASE_SERVICE_ROLE_KEY.
#
# Shared packages (@abstrack/supabase, PowerSync helpers) read process.env from the
# consuming app’s bundle or Node context — set variables in that app’s .env.local / .env.
# -----------------------------------------------------------------------------