Skip to content

Production Checklist

Last Updated: 2025-01-22

Comprehensive checklist for deploying AccessALI to production environments.

Pre-Deployment

Security

  • Change all default passwords
  • Generate strong NEXTAUTH_SECRET (32+ characters)
  • Generate strong JWT_SECRET (32+ characters)
  • Configure OAuth client IDs and secrets
  • Set up SSL/TLS certificates
  • Configure CORS allowed origins
  • Enable rate limiting
  • Set up firewall rules
  • Disable unnecessary ports
  • Configure security headers

Environment Variables

  • NODE_ENV=production
  • DATABASE_URL (production database)
  • NEXTAUTH_URL (production URL)
  • NEXTAUTH_SECRET (strong secret)
  • JWT_SECRET (strong secret)
  • OAuth credentials (Google, Facebook)
  • Email service credentials (Resend)
  • Set USE_MOCK_* to false

Database

  • Run migrations on production database
  • Set up database backups (automated)
  • Configure connection pooling
  • Set up database monitoring
  • Test database connection
  • Create database indexes
  • Set up read replicas (if needed)

Application

  • Build production Docker image
  • Test image locally
  • Run type check (pnpm type-check)
  • Run linter (pnpm lint)
  • Run all tests (pnpm test)
  • Run E2E tests (pnpm test:e2e)
  • Verify all environment variables
  • Test health check endpoint

Deployment

Docker Deployment

# Build production image
docker build -f Dockerfile -t accessali:production .

# Tag for registry
docker tag accessali:production registry.example.com/accessali:v1.0.0

# Push to registry
docker push registry.example.com/accessali:v1.0.0

# Deploy
docker-compose -f docker-compose.prod.yml up -d

Kubernetes Deployment

# Create namespace
kubectl create namespace accessali

# Create secrets
kubectl create secret generic accessali-secrets \
  --from-env-file=.env.production \
  -n accessali

# Deploy
kubectl apply -f k8s/ -n accessali

# Verify
kubectl get pods -n accessali
kubectl get services -n accessali

Vercel Deployment

# Install Vercel CLI
npm install -g vercel

# Login
vercel login

# Deploy
cd src
vercel --prod

# Or use GitHub integration
# Push to main branch triggers deployment

Post-Deployment

Verification

  • Application is accessible at production URL
  • Health check endpoint returns 200 (/api/health)
  • Login works with email/password
  • OAuth login works (Google, Facebook)
  • Database connection is stable
  • Static assets load correctly
  • API routes respond correctly
  • Check browser console for errors
  • Test on mobile devices
  • Verify SSL certificate

Monitoring

  • Set up application monitoring (Vercel Analytics, New Relic, etc.)
  • Configure error tracking (Sentry)
  • Set up log aggregation (CloudWatch, Datadog, etc.)
  • Configure uptime monitoring (Pingdom, UptimeRobot)
  • Set up database monitoring
  • Configure alerting for critical errors
  • Set up performance monitoring

Backup

  • Verify database backups are running
  • Test backup restoration process
  • Set up off-site backup storage
  • Document backup retention policy
  • Schedule regular backup tests

Performance

Optimization

  • Enable Next.js caching
  • Configure CDN for static assets
  • Enable image optimization
  • Set up Redis caching
  • Configure database query caching
  • Implement rate limiting
  • Enable compression (gzip/brotli)
  • Optimize Docker image size
  • Set resource limits (CPU, memory)

Scalability

  • Configure horizontal pod autoscaling (Kubernetes)
  • Set up load balancing
  • Configure database connection pooling
  • Implement caching strategy
  • Set up read replicas (if needed)
  • Test under load

Security Checklist

Application Security

  • All inputs validated with Zod
  • SQL injection prevention (using Prisma)
  • XSS prevention (React escaping)
  • CSRF protection enabled
  • Secure headers configured
  • Rate limiting enabled
  • Authentication required for protected routes
  • Session security configured

Infrastructure Security

  • HTTPS/TLS enabled
  • Firewall configured
  • Network policies in place
  • Secrets stored securely (not in code)
  • Access controls configured (RBAC)
  • Security patches applied
  • Vulnerability scanning enabled
  • DDoS protection configured

Disaster Recovery

Backup Strategy

  • Database: Daily automated backups
  • Backups tested monthly
  • Recovery time objective (RTO) defined
  • Recovery point objective (RPO) defined
  • Backup retention policy documented
  • Off-site backup storage configured

Incident Response

  • Incident response plan documented
  • On-call rotation configured
  • Escalation procedures defined
  • Runbook for common issues
  • Rollback procedure tested

Compliance

  • Privacy policy published
  • Terms of service published
  • Cookie consent implemented
  • Data retention policy defined
  • GDPR compliance (if applicable)
  • Accessibility standards met (WCAG 2.1)
  • Security audit completed

Documentation

  • Production architecture documented
  • Deployment process documented
  • Rollback procedure documented
  • Monitoring and alerting documented
  • On-call procedures documented
  • API documentation up to date
  • User documentation available

Go-Live

Final Checks

  • All checklist items completed
  • Stakeholders notified
  • Support team briefed
  • Monitoring dashboards ready
  • Incident response team on standby
  • Communication plan ready
  • Rollback plan ready

Launch

# 1. Final verification
curl https://accessali.example.com/api/health

# 2. Monitor logs
kubectl logs -f deployment/accessali-app -n accessali

# 3. Monitor metrics
# Check dashboards for errors, latency, traffic

# 4. Verify key workflows
# - User registration
# - Login
# - Dashboard access
# - Property viewing

Post-Launch

  • Monitor application metrics
  • Watch error rates
  • Check database performance
  • Verify backups ran successfully
  • Send launch announcement
  • Schedule post-launch review

Rollback Procedure

If issues arise:

# Kubernetes
kubectl rollout undo deployment/accessali-app -n accessali

# Docker Compose
docker-compose -f docker-compose.prod.yml down
docker-compose -f docker-compose.prod.yml up -d --force-recreate

# Vercel
vercel rollback

Support Contacts