Deployment Guide

Comprehensive guide to deploying Refresh App Web across environments.

Environments

Environment	URL	AWS Account	Cloudflare Worker	Auto-Deploy
PR Sandbox	[pr-num].dev.app.refresh.tech	469718319213	app-web-dev-sandbox	On PR creation
Development	dev.app.refresh.tech	469718319213	app-web-development	On merge to main
Staging	staging.app.refresh.tech	328237344502	app-web-staging	After dev deployment
Production	app.refresh.tech	231307122957	app-web-production	After staging deployment

Deployment Pipeline

PR Created → PR Sandbox Deploy
     ↓
PR Merged to main → Dev Deploy → Staging Deploy → Production Deploy

CI/CD Workflow

GitHub Actions workflows automate deployments. See Architecture: Cloudflare Deployment for pipeline details.

Manual Deployment

Prerequisites

1. Wrangler CLI installed:

npm install -g wrangler

1. Authenticated to Cloudflare:

wrangler login

1. AWS credentials configured:

aws configure sso --profile ref-dev

Deploy to Development

# Fetch environment variables
./scripts/fetch-ssm-params.sh dev .dev.vars

# Run migrations
pnpm db:migrate

# Build and deploy
pnpm build
npx wrangler deploy --env development

Deploy to Production

# Fetch environment variables
./scripts/fetch-ssm-params.sh production .prod.vars

# Run migrations (CAUTION)
WRITE_DATABASE_URL=$PROD_DB_URL pnpm db:migrate

# Build and deploy
pnpm build
npx wrangler deploy --env production

Database Migrations

Migrations apply to read replicas first, then write region. See Architecture: Database Architecture.

Rollback Procedure

Rollback Deployment

# List recent deployments
npx wrangler deployments list --env production

# Rollback to previous deployment
npx wrangler rollback --message "Rolling back due to issue" --env production

Rollback Database Migration

1. Create down migration:

-- Reverse the changes
ALTER TABLE users DROP COLUMN phone_number;

1. Apply manually:

psql $WRITE_DATABASE_URL -f rollback.sql

Monitoring Deployments

1. Check Cloudflare Dashboard:

   • Workers & Pages → app-web-production

   • View deployment status

2. Check GitHub Actions:

   • Actions tab → Recent workflow runs

   • View logs for errors

3. Check application:

   • Visit deployment URL

   • Verify functionality

Troubleshooting

Deployment Failed

1. Check GitHub Actions logs

2. Verify AWS SSM parameters exist

3. Check Cloudflare API token permissions

4. Review build errors in logs

Migration Failed

1. Check database connectivity

2. Verify migration SQL syntax

3. Review RLS policies

4. Check role permissions

Related Documentation

• Environment Management

• Monitoring

• Troubleshooting

---

Last updated: October 2025