vercel-multi-env-setup

# Vercel Multi-Env Setup ## Overview Configure Vercel's three built-in environments (Development, Preview, Production) with scoped environment variables, branch-specific preview URLs, and custom environments for staging. Uses Vercel's native environment system and the REST API for automation. ## Prerequisites - Vercel project linked and deployed - Separate database instances per environment (recommended) - Access to Vercel dashboard or VERCEL_TOKEN for API ## Instructions ### Step 1: Understand Vercel's Environment Model Vercel provides three built-in environments: | Environment | Trigger | URL Pattern | Use Case | |-------------|---------|-------------|----------| | Production | Push to production branch | `yourdomain.com` | Live traffic | | Preview | Push to any other branch | `project-git-branch-team.vercel.app` | PR review | | Development | `vercel dev` locally | `localhost:3000` | Local dev | ### Step 2: Scope Environment Variables ```bash # Add a variable scoped to Production only vercel env add DATABASE_URL production # Enter: postgres://prod-host:5432/myapp # Add a variable scoped to Preview only vercel env add DATABASE_URL preview # Enter: postgres://staging-host:5432/myapp_staging # Add a variable scoped to Development only vercel env add DATABASE_URL development # Enter: postgres://localhost:5432/myapp_dev # Add a variable available in ALL environments vercel env add NEXT_PUBLIC_APP_NAME production preview development # Enter: My App # List all env vars w...