Files
Sauci/apps/mobile/.env.example
T
jjbrunton 006761d3b0 feat(backend): add standalone data plane
Replace the Supabase application data plane with the Node/PostgreSQL API, migrate mobile, admin, web, and MCP callers, add controlled cutover tooling, and define hardened Dokploy infrastructure.
2026-08-28 14:42:11 +01:00

26 lines
1.2 KiB
Bash

# Hosted Supabase Auth configuration (required). These public values are used
# only for identity; product data always uses EXPO_PUBLIC_API_URL.
# Local/E2E builds may use only the designated non-production Auth project.
EXPO_PUBLIC_SUPABASE_URL=
EXPO_PUBLIC_SUPABASE_ANON_KEY=
# Standalone Sauci product API (required). Supabase is used for Auth only.
# iOS simulator: http://127.0.0.1:3003
# Android emulator: http://10.0.2.2:3003
EXPO_PUBLIC_API_URL=http://127.0.0.1:3003
# Authenticated Maestro additionally reads E2E_EMAIL and E2E_PASSWORD from the
# invoking shell. Do not put those credentials in this Expo environment file or
# commit them. The test user must be disposable, onboarding-complete, and have a
# matching profile in the standalone non-production PostgreSQL database.
# Sentry error tracking (optional - get DSN from https://sentry.io)
EXPO_PUBLIC_SENTRY_DSN=
# RevenueCat (for in-app subscriptions)
# Get your API keys from https://app.revenuecat.com
EXPO_PUBLIC_REVENUECAT_IOS_API_KEY=
EXPO_PUBLIC_REVENUECAT_ANDROID_API_KEY=
# Entitlement ID from RevenueCat dashboard (defaults to "pro" if not set)
EXPO_PUBLIC_REVENUECAT_ENTITLEMENT_ID=Sauci Pro