I agree this is a good approach, but many companies use something like Heroku, which doesn't allow this kind of fine-grained control.
Kind of scary how few people know how to set up nginx anymore.
Kind of scary how few people know how to set up nginx anymore.
Switch to at least 2x-sized dynos and use nginx-buildpack (https://github.com/ryandotsmith/nginx-buildpack) with multi-buildpack (https://github.com/ddollar/heroku-buildpack-multi).
You'll probably need to modify/fork the ruby buildpack to do asset compiles twice (if necessary) and check-in both apps into the same repo. And of course modify the nginx configuration.
You should also be able to setup a heroku nginx app that proxies to other heroku apps.
http://www.youtube.com/playlist?list=PLjQo0sojbbxUav7I746f0l... /shameless self promotion
I recommend using Ubuntu server and using the BrightBox PPA to install 2.1. Updates are an apt-get away, and adding PPAs is far easier to do with configuration management than managing rbenv or rvm.
I use rbenv in development and it's a godsend. I keep it the hell away from production, though.
Getting OS support for brand new software packages is tough. It's not just the package itself that needs support but all the things that depend on it.
If you have to use red hat, then you should probably either stick with 2.0 or just use rbenv until a proper package is released.