So as somebody who has experienced their share of headaches deploying Rails apps (and ended up learning how to provision a VPS from scratch as a result) I'm interested in the questions Peter Cooper of Ruby Inside asks:
- Is there / why isn't there a version of mod_ruby that doesn't have the "class sharing" issue? What is the technical impediment?
- Is there any immutable reason that Ruby apps couldn't, in the future, be deployed in a PHP-esque fashion?
The ensuing discussion in the comments is very instructive, and I've even been giving Cooper's Switchpipe project a bit of attention lately. But Ezra Zygmuntowicz chimed in with quite welcome news:
I'm just going to say that Rubinius has support (as of today!) for running multiple instances of it's VM within one process, each VM on it's own *native* thread, each VM running many ruby green threads. Each VM has it's own heap and so each VM could load different apps that wouldn't interfere with each other. We have plans for a mod_rubinius for apache that takes full advantage of this feature. Stay tuned ;)
I certainly will!
Read this article
