Alle Anleitungen
Deployment

The production launch checklist

Twenty minutes of checks that prevent the most common day-one disasters: secrets, backups, monitoring, security headers and a rollback plan.

Von AI Workspace Team

2 Min. Lesezeit

Shipping is exciting. Losing a database on launch day is not. Run through this list before you announce anything — you can even paste it into an agent and ask it to check your repo against it.

Secrets and configuration

  • No secrets in the repository. Search the history: git log -p | grep -i "secret\|api_key\|password".
  • Every secret is set as an environment variable on the server, and different from development.
  • Debug modes and verbose error pages are off in production.
  • Test API keys (Stripe sk_test_…) are swapped for live ones only when you're ready to take money.

Data and backups

  • Automatic database backups run daily and go off the server (S3, R2, B2).
  • You have restored a backup at least once. An untested backup is a hope, not a backup.
  • Migrations run automatically before each deploy.

Security

  • HTTPS everywhere, HTTP redirects to HTTPS.
  • Only ports 22, 80 and 443 are open to the internet.
  • SSH uses keys, and password login is disabled.
  • Sign-up, sign-in and password reset are rate-limited.
  • Security headers are set (Strict-Transport-Security, X-Content-Type-Options, a Content Security Policy).
  • Dependencies are up to date: npm audit (or your stack's equivalent) shows nothing critical.

Monitoring

  • An uptime monitor pings your health endpoint every minute and alerts you.
  • Errors are reported somewhere you'll actually see them.
  • You know where the logs are and how to search them.
  • Disk usage alerts are set — full disks take servers down silently.

Performance and SEO

  • Pages have titles, descriptions and Open Graph images.
  • Images are compressed and sized for the screen.
  • Static assets are cached; a CDN (for example Cloudflare) sits in front if you expect traffic spikes.

Rollback plan

  • You can redeploy the previous version in one click (Coolify keeps earlier deployments).
  • Database migrations can be rolled back, or are backwards-compatible with the previous release.
  • Someone other than you knows how to do the above.

Launch

Ship it, watch the logs for the first hour, and celebrate. Then go back to the task board — the next feature is waiting.

Bau deine nächste App mit allen Agenten gleichzeitig

Planen, bauen, prüfen und deployen — alles in einem Arbeitsbereich.

Deviloop holen