The Twelve Factor App: Best Practices for JRuby Deployment
summary
Argues JRuby deployments work best as portable executable artifacts not heavy containers so make jar not war and favor executable jar slugs on Heroku. Shows a Netty JRuby app wired with JBundler and Warbler, builds with distinct build / release / run steps, deploys via git push producing slugs, starts in under 30 seconds, supports one-off Heroku run shells, and uses environment variables for all secrets allowing quick rollbacks via Heroku releases.
AI-written summary · about
chapters (15)
- 0:00Start
- 1:48Traditional Model for Jvm Deployment
- 6:48A Single Repository for Multiple Applications
- 8:00Dependencies
- 8:47J Bundler
- 11:32Environment Variables
- 12:43Build Release and Run
- 14:58Deploying to Heroku
- 17:11Creating a Heroku App
- 18:40Heroku Run To Start a One-Off Process on the Heroku Server
- 19:19Processes
- 20:51Concurrency
- 22:04Disposability
- 24:29Dev Prod Parody
- 26:49Recap
related talks
40mSelf-Contained, Source-Free, Executable Ruby Applications with Warbler
25mWhy I like JRuby (and you should too)
28mDeploy, Scale and Sleep at Night with JRuby
31mExpand your Ruby Potential with JRuby
55mJRuby in 2018: Building, Deploying, and Scaling Your Apps
39mJRuby: What Why How ... Do it Now!
39mJRuby on Rails: From Zero to Scale
49mJRuby Everywhere! Server, Client, and Embedded