Deploying Rails is Easier Than it Looks
summary
Claim: a typical Rails app runs on one VPS with EngineX, Unicorn, and PostGres; provisioning uses Chef Solo and takes about twenty minutes with a single bootstrap command; deployment uses Git + cap production deploy to get zero‑downtime releases. The presenter shows a real server web3.makeitwithcode.com returning a Welcome to EngineX page, cites cost savings versus Heroku, estimates ~1.5 hours to first working server and stresses monitoring via Monit and simple checks.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:13Why Heroku
- 2:07Terminology
- 2:35Behind the Scenes
- 2:50Single VPS
- 4:03App Server
- 4:39Database Server
- 4:53Recap
- 7:13My experience
- 9:10Configuration management tools
- 12:08Dont repeat yourself
- 13:06Heroku
- 17:40Monitoring
- 19:36nginx
- 21:37ChefSolo
- 23:18Next Steps
related talks
40mDeploying any Rails application to any cloud in minutes
35mTen Years of Rails Deployment
39mZero downtime deploys for Rails apps
45mLarge-Scaled Deploy Over 100 Servers in 3 Minutes
20mRails Conf 2013 Engine Yard Cloud by Edward Chiu & PJ Hagerty
34mGuide to Continuous Deployment with Rails
56mDeploy and Manage Ruby on Rails Apps on AWS
36mContinuous Deployment with Rails
