©Mettusr, 123RF.com
The Ruby Version Manager (RVM) hands-on
Quick Change!
The success of Rails has helped Ruby establish itself in web hosting stacks along with other script languages such as PHP, Perl, and Python. Although most Linux distributions offer a prebuilt Ruby package, developers and administrators might experience issues if the need arises to use multiple Ruby versions in parallel.
Additionally, choosing among the range of possible Ruby interpreters and versions becomes increasingly confusing. The classic Ruby interpreter – often referred to as "Matz's Ruby Interpreter," or MRI [1], after its main developer – is currently maintained in two branches, 1.8 and 1.9, because of changes that break its backward compatibility.
Projects that rely on Ruby 1.8 often use the Ruby Enterprise Edition (REE) [2], which adds an improved garbage collector, for live applications. Java-related and performance-critical projects use JRuby [3], a Ruby implementation in Java that leverages Java bindings in a Rails project.
RubyGems [4] is a de facto standard for extensions, comparable to Perl CPAN, PHP PEAR, and Python Eggs. Gems are managed via a separate package manager, which initially facilitates their use but can cause clutter in multiple projects with different Gem dependencies.
RVM [5] offers a solution for this complex interplay of Ruby interpreters, versions, and Gems, by helping developers maintain project-based environments.
Installation
The standard installation of RVM is a simple, although unusual, task for the administrator. As is often the case in the Ruby/Rails world, the installation script is executed directly on the network. You simply need to install Git
...Buy this article as PDF
(incl. VAT)
Buy ADMIN Magazine
Subscribe to our ADMIN Newsletters
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Most Popular
Support Our Work
ADMIN content is made possible with support from readers like you. Please consider contributing when you've found an article to be beneficial.

