This article needs additional citations for verification. (February 2012)
|Developer(s)||Wayne E. Seguin, Michal Papis|
1.29.12 / January 15, 2022
|Written in||Bash, Ruby|
|License||Apache License 2.0|
The entire Ruby environment including the Ruby interpreter, installed RubyGems (gems), and documentation is partitioned. A developer can then switch between the different versions to work on several projects with different version requirements. In addition to MRI, the standard Ruby interpreter, RVM functions as an installer for various other implementations of Ruby. These include JRuby, mruby, MacRuby, IronRuby, Maglev, Rubinius, Ruby Enterprise Edition, Topaz, and GoRuby (an interpreter optimized for code golf). In addition, RVM supports the installation of patched versions of MRI.
RVM provides features for organization of Ruby gems through "gemsets", collections of gems separated by a namespace and associated Ruby installation. Gemsets can be associated with directories/projects through the use of the RVM-exclusive
.rvmrc file. An alternative to using the
.rvmrc file (and the general purpose although user-specific
.jrubyrc) and its format is use of the
.ruby-gemset files, which are compatible with other ruby version managers, such as RBenv and chruby. Additionally, using
.rvmrc requires trusting to prevent execution of unauthorized code, while
.ruby-version does not.
- "rvm / RubyGems.org". Retrieved 2016-05-30.
- Thomas, Dave (2011). Programming Ruby 1.9 (Version 4.1 ed.). The Pragmatic Programmer.
- "RVM: Ruby Version Manager - Typical RVM Project Workflow".