RVM: Ruby Version Manager - RVM Ruby Version Manager - Documentation _Internet

Support RVM is maintained by community of volunteers, report issues to RVM issues tracker. If you can help or wish to become one of the maintainers - just start helping. You can find more RVM related projects at RVM Github organization. Donation Love RVM? Help us maintain RVM, a donation can help with it. Want to help in other way, want to be a sponsor? contact: Michal Papis Sponsors Carbon Ads Ruby Version Manager (RVM) RVM is a command-line tool which allows you to easily install, manage, and work with multiple ruby environments from interpreters to sets of gems. Cut Rubies with ease! Install GPG keys: gpg2 --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 7D2BAF1CF37B13E2069D6956105BD0E739499BDB In case you encounter an issues or want to know more, check security Install RVM: \curl -sSL https://get.rvm.io | bash -s stable For installing RVM with default Ruby and Rails in one command, run: \curl -sSL https://get.rvm.io | bash -s stable --rails For more details and troubleshooting visit the installation documentation, and read about the new autolib features watch the most accurate (but not official) rvm screencast read the most accurate (but not official) rvm cheat sheet starting with Rails? watch the RailsCasts.com on Getting Started with Rails Community Maintained Project RVM is maintained and supported by the community via issue trackers and pull requests: on each project in RVM Github organization, especially RVM project issues tracker. Production RVM lets you deploy each project with its own completely self-contained and dedicated environment, from the specific version of ruby, all the way down to the precise set of required gems to run your application. Having a precise set of gems also avoids the issue of version conflicts between projects, which can cause difficult-to-trace errors and hours of hair loss. With RVM, NO OTHER GEMS than those required are installed. This makes working with multiple complex applications, where each has a long list of gem dependencies, much more efficient. RVM lets you easily test gem upgrades, by switching to a new clean set of gems to test with, while leaving your original set intact. It is flexible enough to even let you maintain a set of gems per environment, or per development branch, or even per individual developer's taste! Development RVM reduces the complexity of the many facets of ruby development through its command-line API. With RVM, you can have **identical** self-contained environments in your Development, CI, Q/A, Staging, and Production environments. No more hidden gotchas: if it works for one of them, it will work in all of them. With named gemsets, you can reliably and immediately push changes from one environment to another. And, RVM is for Ruby applications, *not just for Rails*! Any Ruby based application will benefit from your use of RVM. Testing RVM enables you to easily test both upgrade and escape paths very easily and consistently. With RVM, you can run a test suite, rake tasks, benchmarks and gem commands against multiple ruby versions at the same time. This means that you can easily ensure your applications work in Ruby 1.8.X, REE, MRI 1.9.1, jruby, etc... and quickly expose any areas in which they do not. Gem Management RVM has an extremely flexible gem management system called Named Gem Sets. RVM's 'gemsets' make managing gems across multiple versions of Ruby a non-issue. RVM lets you add a small text file to your application's repository, instead of checking in tons of gems which would needlessly inflate your repository size. Additionally, RVM's gemset management uses a common cache directory, so only one downloaded version of each gem resides on disk rather than several copies. RVM helps ensure that all aspects of Ruby are completely contained within user space, strongly encouraging safer, non-root use. Use of RVM rubies thus provides a higher level of system security, and therefore reduces risk and cuts overall system downtime. Additionally, since all processes run at the user level, a compromised ruby process cannot compromise the entire system. Support RVM is continuously evolving, thanks to community pull requests to the project. RVM Documentation Index | RVM Blog Search: RVM About Autolibs Basics Best Practices Cli Configuration Info Install Myths Offline Prerequisites Security Upgrading Interpreters MRI/YARV (ruby) JRuby (jruby) Rubinius (rbx) Rubies Alias Default Docs Info Installing List Named Patching Removing Rubygems Strings Uninstalling Upgrading Gemsets Basics Clear Copying Creating Deleting Emptying Exporting Global Ignoring Importing Initial Listing Using Set Actions do tests benchmark Workflow Chruby Completion Examples Hooks Irbrc Projects Prompt Proxy Rvmrc Screen Scripting Subshells Deployment Best Practices Capistrano Chef Cron God Init D Passenger Integration Bundler Capistrano Chef Cron Culerity Databases Emacs Engineyard Fish Gnome Terminal God Heroku Init D Jenkins Konsole Lxterminal Macports Before Autolibs Macports Memprof Passenger Pow Qtruby Scripting Simple Terminal Sketchup Sudo Teamcity Textmate Tk Ubuntu On Windows Vagrant Vim Xterm Zsh Packages Presentations MWRC 2010 RailsConf 2012 RailsConf 2013 Changelog 66 with Wayne RVM 2: Lessons and future RVM 2: Python Version Manager Changelog 102 with Michal Help & Support Issues tracker FAQ & Notes Troubleshooting Fixing Broken SSL Certificates Quality Assurance Software_testing Development Contributing Debugging Github List Credits Contributions Donations Funding ∞ Copyright © 2009-2011 Wayne E. Seguin © 2011-2017 Michal Papis © 2016-2017 Piotr Kuczynski ∞ Built with Nanoc ∞ Cached by Fastly ∞ Tested by Travis CI