dopplerlisted

# Doppler — Env Var Management Centralize secrets across projects. Rotate once, propagates everywhere. ## When to use - Project has `.env.local` / `.env.vercel` with 5+ secrets - Secrets are reused across multiple projects (API keys, OAuth creds) - Fresh Windows install — need to restore env vars fast ## Prereqs (auto-check before any action) ```bash # 1. CLI installed? doppler --version 2>&1 | head -1 # If not: winget install doppler.doppler (Windows) # OR: brew install dopplerhq/cli/doppler (macOS) # 2. Logged in? doppler me 2>&1 | head -3 # If "Doppler Error: you must provide a token" → run `doppler login` (browser flow, user does this) # 3. Inside a linked repo? test -f doppler.yaml && echo "linked: $(cat doppler.yaml | grep project | awk '{print $2}')" || echo "not linked" ``` Do not proceed if any prereq fails. Tell the user exactly what to run. ## Architecture — hub/spoke on Developer plan **Free tier caps at 10 projects.** Plan for this — consolidate with branch configs. ``` Hubs (secrets live here): ai-keys/prd — shared LLM/API keys (Gemini, OpenAI, Anthropic, Perplexity, Resend) accounts/prd — shared passwords + gmail aliases stripe — dev config (test mode), prd config (live mode) supabase — 1 branch config per Supabase project: prd_<name> Spokes (one Doppler project per app): app-<name>/prd — values are ${ref://hub.config.KEY} cross-project references ``` **Cross-project refs** (`${project.config.SECRET}`)