How To Install Ruby 2.1.0 On CentOS 6.5 Using RVM

Whether you are preparing your VPS to try out a new application, or find yourself in need of a solid and isolated Ruby installation, getting your system ready-for-work (inline with CentOS design ideologies of stability, along with its incentives of minimalism) can get you feeling a little bit lost.

In this DigitalOcean article, we are focusing on the simplest and quickest rock-solid way to get the latest Ruby interpreter (version 2.1.0) installed on a VPS running CentOS 6.5 using the Ruby Version Manager - RVM.

Ruby Version Manager, or RVM (and rvm as a command) for short, lets developers and system administrators quickly get started using Ruby and/or developing applications with a Ruby interpreter.

Not only does RVM support multiple versions of Ruby simultaneously, but also it comes with built-in tools to create and work with virtual environments called gemsets. With the help of RVM, it is possible to create any number of perfectly isolated - and self-contained - gemsets where dependencies, packages, and the default Ruby installation are crafted to match your needs and kept accordingly between different stages of deployment – guaranteed to work the same way regardless of where.

CentOS operating system is derived from RHEL - Red Hat Enterprise Linux. The target users of these distributions are usually businesses, which require their systems to be running the most stable way for a long time.

The main incentives of CentOS, therefore, is the desire for stability, which is achieved by supplying tested, stable versions of applications.

All the default applications that are shipped with CentOS remain to be used by the system (and its supportive applications such as the package manager YUM) alone. It is neither recommended nor easy to try to work with them.

That is why we are going to prepare our CentOS 6.5 running droplet with necessary tools and continue with installing a Ruby interpreter targeted to run your applications.

If you are working with multiple applications which are already in production, it is a highly likely scenario that at some point you will need to use a different version of Ruby for a certain application.

However, for most situations, you will probably be using the latest version as the interpreter to run all others.

One of RVM’s excellent features is its ability to help you set a default Ruby version to be used generally and switch between them when necessary.

To check your current default interpreter, run the following:

ruby --version
# ruby command is linked to the selected version of Ruby Interpreter (i.e. 2.1.0)

To see all the installed Ruby versions, use the following command:

rvm list rubies

To set a Ruby version as the default, run the following:

# Usage: rvm use [version] --default
rvm use 2.1.0 --default

To use another version for the current session, omit the --default flag:

# Usage: rvm use [version]
rvm use 2.1.0

RVM gemsets consist of virtual environment at physical locations whereby all application related packages (e.g. dependencies, libraries etc.) are kept and used by a single application (i.e. your website).

Although for developers new to the concept, using gemsets (or environments) might appear like an unnecessary, cumbersome process at first. As you continue to develop and produce your application, however, the benefits soon start to become visible. Once you start using environments, both for the production and the development stages of application, it should become a little bit simpler to maintain.

In order to create a new gemset to contain a Ruby application, run the following commands:

# Usage: rvm gemset [create/use] [name]
# Create a new gemset using the default Ruby interpreter (2.1.0)
# Run: rvm use [version] if you wish to work with another
# Example: rvm use 2.0.0
rvm gemset create myapp

# Switch to using the new gemset called *myapp*
rvm gemset use    myapp

To simplify the above process, you can alternatively go with:

# Usage: rvm use [version]@[name] --create
rvm use 2.1.0@myapp --create

From this point on, all the actions you take (i.e. installing a Ruby gem) will concern your newly created environment alone. For example, installing a gem via:

gem install [package]

translates to having [package] installed inside the gemset, restricting other applications’ (i.e. from other gemsets) access.

If you ever need to wipe all the gems installed, you can empty the gemset with the following command:

# Usage: rvm gemset empty [name]
rvm gemset empty myapp

Likewise, deleting a gemset can be done by using the delete argument passed to rvm:

# Usage: rvm gemset delete [name]
rvm gemset delete myapp

Note: To learn more about using RVM, you can check out our detailed tutorial on the subject by clicking here.

<div class=“author”>Submitted by: <a href=“https://twitter.com/ostezer”>O.S. Tezer</a></div>