PROVIDER - Minimal Ruby version manager

rbenv

rbenv switches Ruby versions with a few hundred lines of shell, uses .ruby-version for directory-level conventions and shim forwarding while leaving system Ruby clean; it cannot install versions alone, needs ruby-build and leaves Gem isolation to bundler.

Developer Tools United States 2026.11.19
3.9pts

Detailed Notes

Pros 5 items

Switches Ruby versions with a shell script core kept under 500 lines
Applies directory-level versions through 1 .ruby-version file automatically
Delegates compiled installs to the ruby-build plugin with 2 custom build flag categories
Forwards commands through shims with 0 changes to the system Ruby
A plugin ecosystem of 20+ extensions includes rbenv-gemset and rbenv-vars

Cons 4 items

It cannot install versions by itself and needs ruby-build
Compiling takes time, so the first experience trails prebuilt distributions
No dependency isolation, so Gem separation still needs bundler or gemsets
Windows support is missing and requires WSL or a third-party port

Service Overview

rbenv is the widely used version manager in the Ruby community. It is deliberately minimal: the core only selects an interpreter from configuration and forwards commands through shims, leaving compiled installs to the ruby-build plugin.

In the development tools category it represents minimum-responsibility version management: opposite to rvm's all-in-one approach, rbenv pushes complexity into plugins and system tools.

Key Strengths

  • Minimal implementation: a small core with predictable behaviour
  • Directory convention: .ruby-version applies versions automatically
  • Shim forwarding: the system Ruby stays untouched
  • Plugin extensions: 20+ common plugins cover typical needs
  • Long stability: years of evolution with very few behaviour changes

Product Ecosystem

Platform capabilities

Version selection and switching, directory configuration, version listing, shim generation and rehash management.

Integrations

Works with ruby-build, bundler, rbenv-gemset, rbenv-vars, GitHub Actions and mainstream editors.

Typical scenarios

Maintaining projects on multiple Ruby versions, Rails development and pinning interpreters in CI.

Limitations

  • External installer: ruby-build must be installed separately
  • Compile time: first installs of a version are slow
  • No isolation: Gem separation needs bundler or gemsets
  • Windows gap: WSL or a third-party port is required

Use Cases

  • Ruby and Rails projects (★★★★☆): one of the community defaults
  • Multiple versions side by side (★★★★☆): clean and predictable switching
  • All-in-one toolchain needs (★★★☆☆): rvm is broader
  • Windows environments (★★☆☆☆): extra adaptation required

Pricing

Item Price Notes
rbenv itself $0 MIT open source, commercial use allowed
ruby-build $0 Companion plugin, free to use
Commercial support None GitHub issues only

FAQ

Should I choose rbenv or rvm?

Choose rbenv for minimal, predictable behaviour and rvm when you want gemsets, integrated installs and more built-in features.

Why is the install command missing?

rbenv does not ship an install command; add the ruby-build plugin first.

Does it affect the system Ruby?

No, rbenv forwards through shims and leaves the system Ruby intact.

How do I isolate Gems per project?

Use bundler's path configuration or the rbenv-gemset plugin.

Code Examples

# Install rbenv and ruby-build on macOS
brew install rbenv ruby-build

# Install and select a version
rbenv install 3.3.0
rbenv global 3.3.0

# Pin a version for the project
cd my-app && rbenv local 3.3.0
cat .ruby-version

# Show the active version and its source
rbenv version

Community & Resources

Visit rbenv Website → https://github.com/rbenv/rbenv
Visit Website ↗