Deployment Runbook

import { Steps, Aside, Tabs, TabItem } from ‘@astrojs/starlight/components’;

Standard Deployment (Automated)

All deployments run automatically through Vercel + GitHub Actions. The pipeline is:

feature/* → develop → staging → main
                │           │         │
            Preview      Staging   Production

No manual intervention required for standard deployments.

Manual Deployment (Emergency)

1. Go to Vercel project → Deployments 2. Find the target deployment 3. Click "..." → "Redeploy" ```bash npm i -g vercel vercel --prod=false # staging vercel --prod # production ```

Rollback

Option 1: Vercel Instant Rollback (< 60 seconds)

Vercel dashboard → Deployments
Find last known-good deployment
Click “Promote to Production”
Verify: curl -I https://brettjohnson.xyz

Option 2: Git Revert

git checkout main
git revert <bad-commit-sha> --no-edit
git push origin main
# Triggers automatic redeploy + semantic-release PATCH bump

Post-Deployment Verification

# HTTP status check
curl -I https://brettjohnson.xyz

# All key pages
for page in "" "speaking" "consulting" "podcast" "media" "contact"; do
  curl -s -o /dev/null -w "%{http_code} /$page\n" "https://brettjohnson.xyz/$page"
done

# API health
curl https://api.brettjohnson.xyz/api/status

Also check:

Sentry for new errors (wait 5 min post-deploy)
Vercel Analytics for anomalous error rates

DNS Cutover (Launch Day)

1. Confirm Vercel production deployment is ready and healthy

In Cloudflare DNS, verify CNAME records point to Vercel
Test DNS propagation from external network:
Terminal window
```
nslookup brettjohnson.xyz 8.8.8.8
```
Verify HTTPS is working:
Terminal window
```
curl -I https://brettjohnson.xyz
```
Confirm old holding page is no longer serving

DNS propagation is near-instant with Cloudflare (< 1 minute, proxied).