bin | ||
completions | ||
doc | ||
libexec | ||
.gitignore | ||
LICENSE | ||
README.md |
Simple Ruby Version Management: rbenv
Use rbenv to pick a Ruby version for your application and guarantee that your development environment matches production. Put rbenv to work with Bundler for painless Ruby upgrades and bulletproof deployments.
Powerful in development. Specify your app's Ruby version once, in a single file. Keep all your teammates on the same page. No headaches running apps on different versions of Ruby. Just Works™ from the command line and with app servers like Pow. Override the Ruby version anytime: just set an environment variable.
Rock-solid in production. Your application's executables are its
interface with ops. With rbenv and Bundler
binstubs
you'll never again need to cd
in a cron job or Chef recipe to
ensure you've selected the right runtime. The Ruby version
dependency information lives in one place—your app—so upgrades and
rollbacks are atomic, even when you switch versions.
One thing well. rbenv is concerned solely with switching Ruby versions. It's simple and predictable. A rich plugin ecosystem lets you tailor it to suit your needs. Compile your own Ruby versions, or use the ruby-build plugin to automate the process. Specify per-application environment variables with rbenv-vars. See more plugins on the wiki.
Table of Contents
How It Works
rbenv operates on the per-user directory ~/.rbenv
. Version names in
rbenv correspond to subdirectories of ~/.rbenv/versions
. For
example, you might have ~/.rbenv/versions/1.8.7-p354
and
~/.rbenv/versions/1.9.3-p327
.
Each version is a working tree with its own binaries, like
~/.rbenv/versions/1.8.7-p354/bin/ruby
and
~/.rbenv/versions/1.9.3-p327/bin/irb
. rbenv makes shim binaries
for every such binary across all installed versions of Ruby.
These shims are simple wrapper scripts that live in ~/.rbenv/shims
and detect which Ruby version you want to use. They insert the
directory for the selected version at the beginning of your $PATH
and then execute the corresponding binary.
Installation
Compatibility note: rbenv is incompatible with rvm. Things will
appear to work until you try to install a gem. The problem is that
rvm actually overrides the gem
command with a shell function!
Please remove any references to rvm before using rbenv.
If you're on Mac OS X, consider installing with Homebrew.
Basic GitHub Checkout
This will get you going with the latest version of rbenv and make it easy to fork and contribute any changes back upstream.
-
Check out rbenv into
~/.rbenv
.$ git clone git://github.com/sstephenson/rbenv.git ~/.rbenv
-
Add
~/.rbenv/bin
to your$PATH
for access to therbenv
command-line utility.$ echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bash_profile
Zsh note: Modify your
~/.zshenv
file instead of~/.bash_profile
.Ubuntu note: Ubuntu uses
~/.profile
for enabling certain path changes. This file won't be read if you create a~/.bash_profile
. Therefore, it's recommended that you add this line and the one in point 3 below to your~/.profile
. This has the added advantage of working under both bash and zsh. -
Add
rbenv init
to your shell to enable shims and autocompletion.$ echo 'eval "$(rbenv init -)"' >> ~/.bash_profile
Zsh note: Modify your
~/.zshenv
file instead of~/.bash_profile
.Ubuntu note: Same as Ubuntu note for point 2 above.
-
Restart your shell as a login shell so the path changes take effect. You can now begin using rbenv.
$ exec $SHELL -l
-
Install ruby-build, which provides an
rbenv install
command that simplifies the process of installing new Ruby versions.$ rbenv install 1.9.3-p327
As an alternative, you can download and compile Ruby yourself into
~/.rbenv/versions/
. -
Rebuild the shim binaries. You should do this any time you install a new Ruby binary (for example, when installing a new Ruby version, or when installing a gem that provides a binary).
$ rbenv rehash
Upgrading
If you've installed rbenv manually using git, you can upgrade your installation to the cutting-edge version at any time.
$ cd ~/.rbenv
$ git pull
To use a specific release of rbenv, check out the corresponding tag:
$ cd ~/.rbenv
$ git fetch
$ git tag
v0.1.0
v0.1.1
v0.1.2
v0.2.0
$ git checkout v0.2.0
Homebrew on Mac OS X
You can also install rbenv using the Homebrew package manager on Mac OS X.
$ brew update
$ brew install rbenv
$ brew install ruby-build
To later update these installs, use upgrade
instead of install
.
Afterwards you'll still need to add eval "$(rbenv init -)"
to your
profile as stated in the caveats. You'll only ever have to do this
once.
Neckbeard Configuration
Skip this section unless you must know what every line in your shell profile is doing.
rbenv init
is the only command that crosses the line of loading
extra commands into your shell. Coming from rvm, some of you might be
opposed to this idea. Here's what rbenv init
actually does:
-
Sets up your shims path. This is the only requirement for rbenv to function properly. You can do this by hand by prepending
~/.rbenv/shims
to your$PATH
. -
Installs autocompletion. This is entirely optional but pretty useful. Sourcing
~/.rbenv/completions/rbenv.bash
will set that up. There is also a~/.rbenv/completions/rbenv.zsh
for Zsh users. -
Rehashes shims. From time to time you'll need to rebuild your shim files. Doing this on init makes sure everything is up to date. You can always run
rbenv rehash
manually. -
Installs the sh dispatcher. This bit is also optional, but allows rbenv and plugins to change variables in your current shell, making commands like
rbenv shell
possible. The sh dispatcher doesn't do anything crazy like overridecd
or hack your shell prompt, but if for some reason you needrbenv
to be a real script rather than a shell function, you can safely skip it.
Run rbenv init -
for yourself to see exactly what happens under the
hood.
Uninstalling Ruby Versions
As time goes on, ruby versions you install will accumulate in your
~/.rbenv/versions
directory.
There is no uninstall or remove command in rbenv
, so removing old
versions is a simple matter of rm -rf
the directory of the relevant
ruby version you want removed under ~/.rbenv/versions
Usage
Like git
, the rbenv
command delegates to subcommands based on its
first argument. The most common subcommands are:
rbenv global
Sets the global version of Ruby to be used in all shells by writing
the version name to the ~/.rbenv/version
file. This version can be
overridden by a per-project .rbenv-version
file, or by setting the
RBENV_VERSION
environment variable.
$ rbenv global 1.9.3-p327
The special version name system
tells rbenv to use the system Ruby
(detected by searching your $PATH
).
When run without a version number, rbenv global
reports the
currently configured global version.
rbenv local
Sets a local per-project Ruby version by writing the version name to
an .rbenv-version
file in the current directory. This version
overrides the global, and can be overridden itself by setting the
RBENV_VERSION
environment variable or with the rbenv shell
command.
$ rbenv local rbx-1.2.4
When run without a version number, rbenv local
reports the currently
configured local version. You can also unset the local version:
$ rbenv local --unset
rbenv shell
Sets a shell-specific Ruby version by setting the RBENV_VERSION
environment variable in your shell. This version overrides both
project-specific versions and the global version.
$ rbenv shell jruby-1.7.1
When run without a version number, rbenv shell
reports the current
value of RBENV_VERSION
. You can also unset the shell version:
$ rbenv shell --unset
Note that you'll need rbenv's shell integration enabled (step 3 of
the installation instructions) in order to use this command. If you
prefer not to use shell integration, you may simply set the
RBENV_VERSION
variable yourself:
$ export RBENV_VERSION=jruby-1.7.1
rbenv versions
Lists all Ruby versions known to rbenv, and shows an asterisk next to the currently active version.
$ rbenv versions
1.8.7-p352
1.9.2-p290
* 1.9.3-p327 (set by /Users/sam/.rbenv/global)
jruby-1.7.1
rbx-1.2.4
ree-1.8.7-2011.03
rbenv version
Displays the currently active Ruby version, along with information on how it was set.
$ rbenv version
1.8.7-p352 (set by /Volumes/37signals/basecamp/.rbenv-version)
rbenv rehash
Installs shims for all Ruby binaries known to rbenv (i.e.,
~/.rbenv/versions/*/bin/*
). Run this command after you install a new
version of Ruby, or install a gem that provides binaries.
$ rbenv rehash
rbenv which
Displays the full path to the binary that rbenv will execute when you run the given command.
$ rbenv which irb
/Users/sam/.rbenv/versions/1.9.3-p327/bin/irb
rbenv whence
Lists all Ruby versions with the given command installed.
$ rbenv whence rackup
1.9.3-p327
jruby-1.7.1
ree-1.8.7-2011.03
Development
The rbenv source code is hosted on GitHub. It's clean, modular, and easy to understand, even if you're not a shell hacker.
Please feel free to submit pull requests and file bugs on the issue tracker.
Version History
0.3.0 (December 25, 2011)
- Added an
rbenv root
command which prints the value of$RBENV_ROOT
, or the default root directory if it's unset. - Clarified Zsh installation instructions in the readme.
- Removed some redundant code in
rbenv rehash
. - Fixed an issue with calling
readlink
for paths with spaces. - Changed Zsh initialization code to install completion hooks only for interactive shells.
- Added preliminary support for ksh.
rbenv rehash
creates or removes shims only when necessary instead of removing and re-creating all shims on each invocation.- Fixed that
RBENV_DIR
, when specified, would be incorrectly expanded to its parent directory. - Removed the deprecated
set-default
andset-local
commands. - Added a
--no-rehash
option torbenv init
for skipping the automatic rehash when opening a new shell.
0.2.1 (October 1, 2011)
- Changed the
rbenv
command to ensure thatRBENV_DIR
is always an absolute path. This fixes an issue where Ruby scripts using theruby-local-exec
wrapper would go into an infinite loop when invoked with a relative path from the command line.
0.2.0 (September 28, 2011)
- Renamed
rbenv set-default
torbenv global
andrbenv set-local
torbenv local
. Theset-
commands are deprecated and will be removed in the next major release. - rbenv now uses
greadlink
on Solaris. - Added a
ruby-local-exec
command which can be used in shebangs in place of#!/usr/bin/env ruby
to properly set the project-specific Ruby version regardless of current working directory. - Fixed an issue with
rbenv rehash
when no binaries are present. - Added support for
rbenv-sh-*
commands, which run inside the current shell instead of in a child process. - Added an
rbenv shell
command for conveniently setting the$RBENV_VERSION
environment variable. - Added support for storing rbenv versions and shims in directories
other than
~/.rbenv
with the$RBENV_ROOT
environment variable. - Added support for debugging rbenv via
set -x
when the$RBENV_DEBUG
environment variable is set. - Refactored the autocompletion system so that completions are now built-in to each command and shared between bash and Zsh.
- Added support for plugin bundles in
~/.rbenv/plugins
as documented in issue #102. - Added
/usr/local/etc/rbenv.d
to the list of directories searched for rbenv hooks. - Added support for an
$RBENV_DIR
environment variable which defaults to the current working directory for specifying where rbenv searches for local version files.
0.1.2 (August 16, 2011)
- Fixed rbenv to be more resilient against nonexistent entries in
$PATH
. - Made the
rbenv rehash
command operate atomically. - Modified the
rbenv init
script to automatically runrbenv rehash
so that shims are recreated whenever a new shell is opened. - Added initial support for Zsh autocompletion.
- Removed the dependency on egrep for reading version files.
0.1.1 (August 14, 2011)
- Fixed a syntax error in the
rbenv help
command. - Removed
-e
from the shebang in favor ofset -e
at the top of each file for compatibility with operating systems that do not support more than one argument in the shebang.
0.1.0 (August 11, 2011)
- Initial public release.
License
(The MIT license)
Copyright (c) 2013 Sam Stephenson
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.