This guide will assist you to migrate your Ruby or Rails application from MRI (Matz’s Ruby Implementation) to Rubinius. This guide assumes that you are familiar with Ruby or Ruby or Rails, RubyGems, and Bundler. It also assumes that you can use the command line shell.
The first step in migrating to Rubinius is to install Rubinius. Since you will likely need to switch back and forth between MRI and Rubinius while migrating, the easiest approach is to use a Ruby switcher utility.
The chruby command line tool for
switching between Ruby implementations is recommended for use with Rubinius.
All examples in the guides will use
If you are using OS X, the easiest way to install
is to use the Homebrew package manager
$ brew update $ brew install chruby ruby-install
If you are not using Homebrew or are using a different operating system than OS X, please see the the following:
chruby, add the following to the ~/.bashrc or ~/.zshrc file:
See the documentation for more configuration instructions.
Once you have installed the
ruby-install utility, installing Rubinius is
$ ruby-install rbx 2.2.6
For instructions for installing other Ruby implementations, please see the
Now that Rubinius is installed, you can make it active with the following command:
$ chruby rbx
Most gems that run on MRI should run on Rubinius, with the exceptions noted below. Additionally, Rubinius makes many components of the system available as gems. These include the Rubinius tools for parsing and compiling Ruby code, the Ruby debugger and profiler, and the Ruby standard library. All these gems are pre-installed when you install Rubinius.
Many gems that use C-extensions run fine on Rubinius. The exceptions are ones
that rely on MRI internal data structures. These gems cannot be supported on
Rubinius and include gems like
ruby-prof. Rubinius provides
its own Ruby source debugger and profiler, as well as other tools. See the
tools documentation for more details.
Your Gemfile should work fine with Rubinius but you should run
to force the gem dependencies to be recomputed for Rubinius. Also, if you are
using gems that are incompatible with Rubinius, you can put them in a
platforms block until completing the migration to Rubinius as follows:
# Example platforms block for MRI-specific gems platforms :mri do gem 'ruby-prof' gem 'ruby-debug' end
With few exceptions, Rubinius is expected to be compatible with MRI 2.1. Some features, like keyword arguments, are not yet implemented. Other features may not be implemented because they are unknown and no spec exist for the feature yet. Several standard library components, including Continuation, Ripper, TracePoint, and Tracer, are not yet implemented but may be in the future.
If you encounter an incompatible behavior in Rubinius compared to MRI, it’s most likely a bug. Please open an issue for it.