1 minute read

Context

Ruby projects often depend on specific Ruby versions and gem sets.

RVM (Ruby Version Manager) helps isolate those dependencies so:

  • projects don’t conflict
  • upgrades are controlled
  • development environments stay predictable

This cheatsheet focuses on everyday RVM commands, not edge cases.

Installing and Listing Ruby Versions

List available Ruby versions:

rvm list known

Install a specific version:

rvm install 3.2.2

List installed versions:

rvm list

Set a default Ruby:

rvm --default use 3.2.2

Switching Ruby Versions

Use a Ruby version for the current shell:

rvm use 3.2.2

Use a Ruby version temporarily:

rvm use 3.1.4 --temporary

Check the active Ruby:

ruby -v

Always confirm which Ruby you’re running before debugging issues.

Gemsets

Gemsets isolate dependencies within a Ruby version.

Create a gemset:

rvm gemset create myapp

Use a gemset:

rvm gemset use myapp

List gemsets:

rvm gemset list

Delete a gemset:

rvm gemset delete myapp

Gemsets prevent dependency bleed between projects.

Project-Level Ruby Configuration

Create a .ruby-version file:

echo "3.2.2" > .ruby-version

Create a .ruby-gemset file:

echo "myapp" > .ruby-gemset

When entering the directory, RVM will prompt to trust and switch automatically.

Updating and Maintenance

Update RVM itself:

rvm get stable

Upgrade Ruby:

rvm upgrade 3.1.4 3.2.2

Remove an old Ruby version:

rvm remove 2.7.8

Cleaning unused versions reduces confusion.

Bundler Integration

Install Bundler for the active Ruby:

gem install bundler

Install project dependencies:

bundle install

Bundler respects the active Ruby and gemset.

Debugging Common Issues

Reload RVM environment:

source ~/.rvm/scripts/rvm

Check RVM requirements:

rvm requirements

Diagnose environment issues:

rvm doctor

Many Ruby issues trace back to mismatched versions or gemsets.

Shell Integration Notes

RVM modifies shell behavior.

Common issues arise when:

  • shells aren’t loading RVM scripts
  • multiple version managers are installed
  • PATH order is incorrect

Avoid mixing RVM with other Ruby managers unless you understand the interactions.

Practical Tips

  • Keep Ruby versions explicit per project
  • Remove versions you no longer need
  • Use gemsets sparingly but intentionally
  • Trust .ruby-version files only from known sources
  • Verify environment before debugging app errors

Environment clarity saves hours.

Takeaways

  • RVM manages Ruby versions and gem isolation
  • A small command set covers most workflows
  • Project-level files improve consistency
  • Most Ruby issues start with environment drift
  • Discipline beats memorization

A clean Ruby environment makes application problems much easier to reason about.

You May Also Enjoy