Skip to main content

Configuration

The core app runs without environment variables. Add environment variables only for the services you want to enable. See .env.example in the repository root for a starter template.

Environment variables

Browser variables

Variables prefixed with VITE_ are embedded in the client bundle at build time. Never place secret keys inside VITE_* variables. Passkeys (WebAuthn) do not require extra VITE_* variables — configure them in the Supabase Dashboard (or supabase/config.toml locally) as described in Cloud sync with Supabase.

Server variables

Configure server-only variables in your hosting provider (for example, Netlify environment variables). Never commit SUPABASE_SECRET_KEY, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, or AI provider keys. Functions prefer SUPABASE_URL, SUPABASE_PUBLISHABLE_KEY, SUPABASE_SECRET_KEY, and STRIPE_PRICE_ID, while retaining backwards-compatible fallbacks for VITE_SUPABASE_URL, VITE_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY, and VITE_STRIPE_PRICE_ID.

Feature detection

The app checks configuration at runtime:
  • Supabase variables enable authentication, Passkeys, cloud sync, and account management.
  • Stripe variables enable Lifetime Premium checkout and status reconciliation.
  • Developer API keys, /api/v1/*, and /api/mcp require Supabase and Netlify Functions.
  • AI capture requires Supabase, Netlify Functions, migrations through 20260922000100_ai_monthly_quota.sql, and either OPENROUTER_API_KEY or ANTHROPIC_API_KEY.
  • Missing optional variables leave the app in local-first mode.

Bark settings

Bark notification settings (Bark server URL, device key, reminder lead time, and per-subscription toggles) are configured per user inside the web app under Settings → Notifications.