deployment-config

# Deployment Configuration

**Purpose:** Configure and optimize Next.js deployments on Vercel with automated validation and best practices.

**Activation Triggers:**
- Deployment failures or errors
- Build performance optimization needed
- Environment variable configuration
- Edge function setup
- vercel.json configuration
- Production deployment preparation
- Custom domain configuration

**Key Resources:**
- `scripts/validate-deployment.sh` - Validate deployment configuration
- `scripts/optimize-build.sh` - Analyze and optimize build performance
- `scripts/setup-env-vars.sh` - Interactive environment variable setup
- `scripts/test-edge-functions.sh` - Test edge function configuration
- `templates/vercel.json` - Production-ready vercel.json templates
- `templates/env-template.md` - Environment variable documentation
- `examples/deployment-patterns.md` - Common deployment scenarios

## Deployment Workflow

### 1. Pre-Deployment Validation

Validate configuration before deploying:

```bash
# Full deployment validation
./scripts/validate-deployment.sh

# Checks performed:
# - vercel.json syntax and schema
# - Environment variables documented
# - Build command configuration
# - Output directory exists
# - Framework detection correct
# - No hardcoded secrets in code
```

### 2. Configure vercel.json

Choose appropriate template based on needs:

```bash
# Generate vercel.json from template
cp templates/vercel.json vercel.json

# Templates available:
# - basic.vercel.json         → Minimal configuration
# - optimized.vercel.json     → Performance optimized
# - edge-functions.vercel.json → With edge/middleware
# - monorepo.vercel.json      → Monorepo setup
```

**Key Configuration Options:**

**Build Settings:**
- `buildCommand` - Override build command (default: `next build`)
- `installCommand` - Custom install command or skip with `""`
- `outputDirectory` - Build output location (default: `.next`)
- `framework` - Force framework detection (usually auto-detected)

**Routin