Running different versions of Ruby on a single server requires a lot of attention to detail. I used to do it, but I didn't use an automated tool like RVM. RVM is great for switching environments, but it is unnecessary when all you need are a static set of environments that change infrequently. Check out ruby-build for this purpose.
In the end, I found the trouble of running two reliable Ruby environments in production did not offset well against the cost of either updating applications to work with the same Ruby version, or running separate virtualized environments at the OS layer. The time spent debugging and updating our environment was too great in comparison to the additional cost of upgrading our software to all run on Ruby 1.9.
Do any of these behave like Python's virtualenv? I really like how virtualenv works, and if I ever want to get semi-serious with Ruby, I'd like to have something similar.
Essentially, the author is upset that the author of rbenv[0] decided to criticize rvm instead of opening tickets and whatnot.
The author then goes on to blame the rbenv author for the year long delay in implementing PROMPT_COMMAND in rvm.
> We could have this code available for rvm users one year ago, possibly we could have a lot more of good solutions if the problems were discussed instead of throwing accusations as it was done by rbenv author.
[+] [-] kawsper|13 years ago|reply
Right now I am looking for an alternative on my servers, because I need different Ruby versions across projects.
It is very interesting history following the development of RVM, to Rbenv and now also Chruby. It seems like 37signals is going the way of Rbenv.
It will be interesting to follow. It seems like a really fundamental problem, that need to be solved for us to build good software.
[+] [-] bradleyland|13 years ago|reply
In the end, I found the trouble of running two reliable Ruby environments in production did not offset well against the cost of either updating applications to work with the same Ruby version, or running separate virtualized environments at the OS layer. The time spent debugging and updating our environment was too great in comparison to the additional cost of upgrading our software to all run on Ruby 1.9.
[+] [-] RegEx|13 years ago|reply
[+] [-] mpapis|13 years ago|reply
[+] [-] RegEx|13 years ago|reply
Essentially, the author is upset that the author of rbenv[0] decided to criticize rvm instead of opening tickets and whatnot.
The author then goes on to blame the rbenv author for the year long delay in implementing PROMPT_COMMAND in rvm.
> We could have this code available for rvm users one year ago, possibly we could have a lot more of good solutions if the problems were discussed instead of throwing accusations as it was done by rbenv author.
[0]: https://github.com/sstephenson/rbenv
[+] [-] manojlds|13 years ago|reply
[+] [-] tamal|13 years ago|reply