Millions of Apps: What we've learned
summary
Heroku reports millions of apps deployed and distills experience into a 12-factor style checklist: keep secrets out of source control, use environment variables (dotenv, foreman, Heroku config), and rotate keys; aim for dev–prod parity (PostgreSQL, pg_backups, matching Ruby versions). Treat logs as data (logplex, l2met, papertrail) for visibility, mount richer error pages for admins, and use monitoring/error services (honeybadger, airbrake, new relic). If secrets leak, purge history with git filter-branch and rotate keys.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:11Millions of apps and 12-factor
- 4:14Secret token exposure risks
- 6:46Using environment variables for secure configuration
- 13:28Config separation benefits
- 13:49Dev-prod parity
- 16:19Reproducible dev with READMEs
- 18:46Performance as visibility problems
- 20:10Logs for visibility
- 24:00Better error pages
- 26:08Key takeaways and Q&A session
related talks
38mMillions of Apps: What we've Learned
43mMillions of Apps: What we’ve Learned
41mTwelve-Factor Apps
44mHow to Write Deployment-friendly Applications
55mHeroku PaaS Apps to Feature your Work in any Language
36mHeroku: A Year in Review
34m7 Missing Factors for Your Production-Quality 12-Factor Apps
39mRunning Ruby Apps