3 ms·
I can see the value of RVM for developers, running the same code against various gemsets and versions of Ruby, I used it this way, but not for deployment, why n
by zppx 16y ago
I can see the value of RVM for developers, running the same code against various gemsets and versions of Ruby, I used it this way, but not for deployment, why not simply compile everything necessary by hand, install the necessary gems, say ruby 1.9.2 with rails 3.0.3 and some other gems, and them use the result to chroot personalized deploys (or containerize them) instead of installing various versions of ruby with one shell script?
EDIT: Well, since you cannot answer in this thread feel free to answer in my first comment in this thread above if you wish.
EDIT2: I found this article about the matter, I found it to be good, I agree with him in the large picture: http://rcrowley.org/articles/dependencies.html http://rcrowley.org/articles/dependencies.html
- samdk 16y agoI'm not really sure I understand your question. RVM is a tool that can do all of that for me, and it's used and vetted by a large community. I don't know why I wouldn't use RVM. RVM automates the compilation step. I'm not sure why I'd want to do that by hand instead. Gem installation is done on a per-app basis using bundler[0] or RVM's gemsets, so the gems for each application are kept separate anyway. Running different applications on different versions of Ruby at once is also easy with project-level rvmrc files. And if for whatever reason you want different RVM installs for different users that's easy too: RVM only installs for a single user by default. Now, granted, I don't do anything like run a shared hosting service, and there may be cases where RVM lacks the flexibility to do what's required, but I've never run into them. [0] http://rubygems.org/gems/bundler http://rubygems.org/gems/bundler
- zppx 16y agoIs it not simple to write a reply, like samdk did, instead of downvoting?