Deploying Your Site

What You'll Learn

Deployment means making your website available on the internet. Vercel hosts your site, handles traffic, provides HTTPS security, and optimizes performance.

The Deployment Process

1. Push code to GitHub
2. Vercel detects the change
3. Vercel builds your site
4. Vercel deploys to servers worldwide
5. Your site is live

Environment Variables

Some information shouldn't be in your code:

• Database passwords
• API keys
• Secret tokens

These go in environment variables—settings that exist on the server but not in your code.

Deliverable: Prepare for Deployment

Purpose: Ensure your project is ready to deploy.

Expert Role: DevOps Engineer

Tools to Use: Bash (npm run build), Grep (search for secrets), File system

Expected Output

• Security audit results
• Build verification
• Pre-deployment checklist

Prompt Template

Act as a DevOps engineer. Prepare our project for Vercel deployment:
1. Check for any hardcoded secrets (there shouldn't be any)
2. Verify all environment variables are documented
3. Make sure the build completes successfully
4. Check for any TypeScript errors
5. Verify all tests pass

Search the codebase for potential secret leaks (API keys, passwords).
List anything that needs fixing before we deploy.

Deliverable: Document Environment Variables

Purpose: Create a reference for required configuration.

Expert Role: DevOps Engineer

Tools to Use: File system (write), Grep (find env usage)

Expected Output

• .env.example file created
• All variables documented

Prompt Template

Act as a DevOps engineer. Create a .env.example file that lists
all required environment variables with placeholder values.

Search the codebase for all environment variable usage, then
create documentation including:
- Supabase URL and keys
- Any API keys we use
- Analytics IDs
- Other configuration

Mark which are required vs optional.
Never include actual secret values.