Operating Rails: what about after you deploy?
summary
A checklist of concrete practices and failures: set up daily DB backups to GitHub Action artifacts (90 days) and test restores, push all deploys from CI/CD not laptops using GitHub Actions CD for minutes‑long lead time, capture errors with Honeybadger/Sentry plus uptime monitoring, collect traces and metrics with Honeycomb/Prometheus and tracing for N+1s, use CDNs like Fastly or Cloudflare, run strong_migrations for live schema changes, and automate Dependabot/Renovate updates to prevent hijacked servers or leaked secrets.
AI-written summary · about
chapters (8)
- 0:00Operating Rails apps
- 3:57Confidence in production
- 6:08Detecting production errors
- 12:47Managing production data
- 18:54Optimizing Rails speed
- 23:29Rails security best practices
- 26:42Lead time and deployments
- 30:16Summary
related talks
31mOperating Rails: What About After You Deploy?
34mGuide to Continuous Deployment with Rails
36mContinuous Deployment with Rails
27mScaling Ruby Applications: Challenges, Solutions and Best Practices
30mKeith and Mario's Guide to Continuous Deployment with Rails
34mStrong Practices for Rails Applications Continuous Delivery
34mIndustrial Rails
51mPatterns & Playbooks to Make Every Commit Production Ready