26 February 2013
I’ve checked in on the progress of using Rubinius with this same method every couple few months for the past year or so. I was always met with the same results…
“not quite yet, we’re working on it”.
Last night I was getting mentally packed for Waza later this week and decided to check in on the state of things so I could ask the right people the right questions in person when we’re all together. Turns out that sometime between last time and this time, they’ve got things working. Boom diggity! And it’s pretty ding-dang easy too! Double boom diggity!
I’m going to assume that if you want to use Rubinius 2.0 that you also have the good sense to want to use Puma 2.0. There are three very simple steps to get up and running with Rubinius 2.0 + Puma 2.0.
Add the Puma gem to your
Tell Heroku to use Puma as your web server in your
Specify Rubinius as your Ruby engine in your
Once you’ve done those things, your workflow is the same as before.
bundle update && git commit -am "Double boom diggity!" && git push heroku master
If you’re changing an existing app from Heroku’s default Ruby (MRI 1.9.x) to Rubinius, you’ll see a message like this when you
git push heroku master.
The important lines are
Old: ruby 1.9.3 and
New: rubinius 2.0.0.rc1. After that, everything the same as before. The bundling starts, etc.
That’s it. You should now be up and running with Rubinius and Puma!
If you have problems, say something in the comments with a link to a gist with your problem output. If you succeed and get up and running in production, let us in the comments too. Tell the world that you love Rubinius/Puma.
I threw together this quick and dirty Rails app from scratch deployed to Heroku to show all this in action. http://heroku-rbx-puma-rails-app.herokuapp.com. I also migrated an existing MRI 1.9.3 app ( The Farmhouse site ) to Rubinius 2.0 to show the migration is easy too.
None of this would be possible without the hard work of Carl Lerche, Yehuda Katz, André Arko, Terrence Lee and the other contributors to Bundler. And a special thanks to Terrence Lee for his dutiful stewardship of the Heroku Ruby Buildpack. Once again, the awesome powers of Open Source make great things possible.
As of this writing “Rubinius 2.0” actually means “Rubinius 2.0.0.rc1” and “Puma 2.0” actually means “Puma 2.0.0b7”. The net result is the same though.