.env.example

# GitHub repo to import data.json and uploads from at build time.
# These are also auto-filled into the CMS GitHub form (read-only).
# Leave blank to skip remote import.
GITHUB_OWNER=
GITHUB_REPO=
GITHUB_TOKEN=
GITHUB_BRANCH=main
# Paths inside the repo (defaults shown)
GITHUB_DATA_PATH=data.json
GITHUB_UPLOADS_DIR=uploads
GITHUB_AUDIO_DIR=audio
GITHUB_BLOG_DIR=blog

# CMS password — used to lock the CMS and encrypt the GitHub token at build time.
CMS_PASSWORD=

# Public site URL (used for meta tags, RSS, sitemap, etc.)
VITE_SITE_URL=

# Supabase (required for newsletter and other backend features).
# For local dev, run `npm run supabase:start` and use the printed values.
# For production, copy from your Supabase project dashboard → Settings → API.
VITE_SUPABASE_URL=
VITE_SUPABASE_ANON_KEY=

# Newsletter confirmation emails (Supabase Edge Function secrets).
# Set these via `npm run supabase:secrets` or `npx supabase secrets set KEY=VALUE`.
SMTP_HOST=
SMTP_PORT=465
SMTP_USER=
SMTP_PASSWORD=
SMTP_FROM_EMAIL=
SMTP_FROM_NAME=
NEWSLETTER_SECRET=
SITE_NAME=

# Internal cron secret — shared between pg_cron (via Vault) and edge functions.
# Generate with: openssl rand -hex 32
# The deploy script syncs this into Vault automatically.
CRON_SECRET=

# Supabase deploy (required for `platformkit deploy` in CI/production).
# Generate an access token at: https://supabase.com/dashboard/account/tokens
# Project ref is the ID from your Supabase dashboard URL.
SUPABASE_ACCESS_TOKEN=
SUPABASE_PROJECT_REF=