.env.example

# --- Read by the app itself (bundled into the client at build time) -------
# Supabase project — Settings → Data API (URL) / Project API keys (anon
# public / "publishable" key). Must be EXPO_PUBLIC_-prefixed to be readable
# in the client bundle at all — that's Expo's own convention, not a mistake.
EXPO_PUBLIC_SUPABASE_URL=https://your-project.supabase.co
EXPO_PUBLIC_SUPABASE_ANON_KEY=your-anon-or-publishable-key

# --- CLI-only — never read by the app, only used when *you* run commands --
# A Supabase personal access token (supabase.com/dashboard/account/tokens),
# used for `supabase secrets set` (pushing GROQ_API_KEY to the weekly-coach
# Edge Function) and similar CLI operations. NOT EXPO_PUBLIC_-prefixed —
# this grants full account-level access and must never be bundled.
SUPABASE_ACCESS_TOKEN=sbp_...

# Your Groq API key (console.groq.com/keys). Never used directly by this
# app — kept here only as a staging value you push to the Edge Function's
# own secret store with:
#   supabase secrets set --project-ref <ref> --env-file <(echo "GROQ_API_KEY=$GROQ_API_KEY")
GROQ_API_KEY=gsk_...

# An Expo personal access token (expo.dev/accounts/[account]/settings/access-tokens),
# used for `eas build` from a non-interactive shell (CI, or any environment
# where `eas login`'s browser flow isn't available).
EXPO_TOKEN=...