Rvm install mac os

∞Installing RVM

RVM supports most UNIX like systems and Windows (with Cygwin or Bash on Ubuntu on Windows). The basic requirements are bash , curl , gpg2 and overall GNU version of tools — but RVM tries to autodetect it and install anything that is needed.

∞Install GPG keys

As a first step install GPG keys used to verify installation package:

In case you encounter an issues check security

∞Basic install

∞Ubuntu

RVM have dedicated Ubuntu package, so please follow instructions posted here: https://github.com/rvm/ubuntu_rvm

If you need a different (newer) version of RVM, after installing base version of RVM check the Upgrading section.

∞Any other system

Install RVM (development version):

Install RVM stable with ruby:

Additionally with rails (poor man’s railsinstaller):

Or with jruby, rails and puma:

To install without rubygems-bundler and rvm gems (and also remove those gems from both global.gems and default.gems):

To install with hirb gem (and also add it to global.gems):

To install with rails and haml gems (and also add them to default.gems):

For a progress bar when downloading RVM / Rubies:

Point to be noted is, there is a backslash before curl. This prevents misbehaving if you have aliased it with configuration in your

If you’re an existing RVM user and you don’t want RVM to attempt to setup your shell to load RVM, you can opt out of this at install time by exporting rvm_ignore_dotfiles=yes, or opt out permanently by setting this in your rvmrc.

∞You can also:

• read the installation documentation below.
• 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.

∞Installation explained

There are three different ways to install and configure RVM.

1. Single-User installations ( recommended ) — For an isolated install within a user’s $HOME, not for root.
2. Multi-User installations — For server administrators — For an installation usable by all users on the system — Please note that Single-User supersedes Multi-User. This also used to be called the System-Wide Install. Using this type of installation without knowledge how umask works is a big security risk.
3. Mixed mode installations — For an installation usable by all users on the system — with isolated rubies/gemsets within a user’s $HOME. Installation instructions are exactly the same as for Multi-User installations, the difference is in users environment.

∞Installation

I recommend you read the installation script yourself. This will give you a chance to understand what it is doing before installing, and allow you to feel more comfortable running it if you do so.

∞1. Download and run the RVM installation script

Installing the stable release version:

To get the latest development state:

Instruct RVM to not change the shell initializations files ‘rc’ / ‘profile’:

Please note that from this point it is user responsibility to add sourcing rvm to appropriate files.

For a Multi-User install you would execute the following:

Note: The Multi-User install instructions must be prefixed with the sudo command. However, once the install is complete, and the instructions to add users to the rvm group is followed, the use of either sudo or rvmsudo is no longer required. The sudo command is only to temporarily elevate privileges so the installer can complete its work. If you need to use sudo or rvmsudo after the install is complete, some part of the install directions were not properly followed. This usually is because people execute the install as root , rather than executing the installation instructions from a non-privileged user account.

Installing a specific version:

Prefix the ‘bash’ portion with ‘sudo’, of course, if you wish to apply this to a Multi_user Install. Please feel free to check out our upgrading docs for more details on branch format.

Debugging installation process:

If the rvm install script complains about certificates you need to follow the displayed instructions.

Single-User Install Location:

If the install script is run as a standard, non-root user, RVM will install into the current users’s home directory.

Modification of user configuration files ( *rc / *profile ) — RVM by default will modify user startup files, although it is not recommended you can disable automated process and do this manually:

Multi-User Install Location: /usr/local/rvm

If the install script is run prefixed with sudo, RVM will automatically install into /usr/local/rvm . Please see the troubleshooting page for an important note regarding Multi-User Installs.

Please see the FAQ page for an important note regarding root only installs.

External tutorials

Note that that any outside tutorials are NOT supported whether they work or not. Tutorials are great, however we have spent massive amounts of man hours debugging the installation process. Please use the install process(es) from this site only, as this is the only supported installation types and methods.

To update an existing RVM installation

It is safe to simply re-run the installation script again, or you can follow the upgrading docs.

∞2. Load RVM into your shell sessions as a function

Single-User:

The rvm function will be automatically configured for every user on the system if you install as single user. Read the output of installer to check which files were modified.

Multi-User:

The rvm function will be automatically configured for every user on the system if you install with sudo. This is accomplished by loading /etc/profile.d/rvm.sh on login. Most Linux distributions default to parsing /etc/profile which contains the logic to load all files residing in the /etc/profile.d/ directory. Once you have added the users you want to be able to use RVM to the rvm group, those users MUST log out and back in to gain rvm group membership because group memberships are only evaluated by the operating system at initial login time. Zsh not always sources /etc/profile so you might need to add this in /etc/**/zprofile :

Mixed mode (user gemsets):

• After following above instructions for Multi-User.
• Select a user as a manager — he will be responsible for installing new rubies. This user should never run the command introduced below. If this happens, remove/rename the $/.rvmrc , logout and then relogin. Otherwise you won’t be able to install/upgrade new rubies correctly.

For each user that want to use RVM, an additional command needs to be run (once) for each user:

Gemsets created by these users will be hosted in their HOME directory. It’s not possible to use global gemsets from system without using tricks like manually linking directories and they should not be used in mixed-mode. Please bear in mind that ‘system’ in this context does not refer to your distribution’s ruby packages, but to the RVM Multi-User installation.

You have two possibilities to manage RVM. The first one is to add managers to the rvm group. The second one is to use separate managers with rvmsudo and privilege escalation. Note that it is not safe to use rvmsudo from mixed mode user. Both can be mixed without any side-effect. It is however very important to not enable mixed-mode gemsets or rubies for the managers. RVM is using a custom umask ( umask u=rwx,g=rwx,o=rx ) when installing gemsets, rubies, updating itself, etc. This should not impact your system. But if you prefer to avoid RVM messing around with your umask, you can comment the umask line in /etc/rvmrc .

This mode should also works with passenger, please follow passenger instructions. .

∞3. Reload shell configuration & test

Close out your current shell or terminal session and open a new one (preferred). You may load RVM with the following command:

If installation and configuration were successful, RVM should now load whenever you open a new shell. This can be tested by executing the following command which should output rvm is a function as shown below.

NOTE: Before reporting problems check rvm notes as it might contain important information.

Congratulations! You have successfully installed RVM.

∞Try out your new RVM installation

Below are some examples of how to install and use a Ruby under RVM.

Display a list of all known rubies. NOTE: RVM can install many more Rubies not listed.

Install a version of Ruby (eg 2.1.1 ):

Use the newly installed Ruby:

Check this worked correctly:

Optionally, you can set a version of Ruby to use as the default for new shells. Note that this overrides the ‘system’ ruby:

∞Enjoy using RVM!

∞Where to now?

If you are new to RVM I recommend that you read the basics page. At the end of the basics page there are further links for getting started.

∞Troubleshooting Your Install

and got the notice

ca-certificates need to be installed:

If you open a new shell and running:

does not show rvm is a function , RVM isn’t being sourced correctly.

Ensure that RVM is sourced after any path settings as RVM manipulates the path. If you don’t do this, RVM may not work as expected.

If you are using GNOME on Red Hat, CentOS or Fedora, ensure that the Run command as login shell option is checked under the Title and Command tab in Profile Preferences. After changing this setting, you may need to exit your console session and start a new one before the changes take affect.

Источник

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: In case you encounter an issues or want to know more, check security
• Install RVM:
• For installing RVM with default Ruby and Rails in one command, run:
• 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.

Источник

How to Install Ruby on macOS with RVM

This article explains why you should avoid using the version of Ruby bundled with macOS and should instead install your own version of Ruby with RVM, the Ruby Version Manager.

Hands Off the System Ruby

Apple bundles the Ruby programming language with macOS. However, the main caveat for using the bundled version, called the system Ruby, is that Apple bundles Ruby for it’s own use. Therefore, it’s best not to make changes to the system Ruby.

You’ll know when you’re about to change the system Ruby when you need to prefix a gem installation with sudo , for example:

Another reason for not using the system Ruby is that it’s often several versions behind the latest stable version.

The Ruby Version Manager

A better alternative to using the system Ruby is to install Ruby with RVM, the Ruby Version Manager. RVM is a tool for installing different versions of Ruby itself. RVM has the following advantages:

1. RVM enables you to install multiple versions of Ruby and allows you to change which version you want to use.
2. RVM installs each version of Ruby in a hidden folder in your home folder so each version of Ruby you install doesn’t affect the system Ruby.
3. Gems installed by RVM-managed versions of Ruby are installed within the hidden folder in your home folder containing that version of Ruby.
4. You won’t need use sudo to install gems.

To check that you’re currently using the system Ruby, open Terminal and type the following:

If you’re using the system Ruby, macOS will respond with:

You can check which version of Ruby macOS is using with:

Installing RVM and Ruby

The RVM install page has comprehensive instructions for installing RVM that work on macOS. I’ll provide the steps I used here.

The first step is to install the mpapis public key. However, as the install page notes, you might need gpg. macOS doesn’t ship with gpg so before installing the public key, you’ll need to install gpg. I installed gpg with Homebrew:

After you’ve installed gpg, you can install the mpapis public key:

I’ve listed the mapis public key install command here for illustration. You should use the version on the RVM install page.

I chose to install RVM with the latest stable version of Ruby, which at the time was 2.2.0:

After the installation completes, close the Terminal window and open a new one to make sure that Terminal picks up any environment changes.

Using RVM

You can list the versions of Ruby available to RVM with rvm list :

The rvm use command selects a version of Ruby:

You can check that you’re using an RVM-managed version of Ruby with:

macOS now responds with:

which tells us we’re using version 2.2.0 and that version 2.2.0 has been installed in my home folder away from the system Ruby. You can confirm this by asking Ruby itself with:

The RVM-managed version of Ruby responds with:

As I mentioned earlier, gems installed with RVM-managed versions of Ruby are located with the Ruby. You can check where gems will be installed with:

The following lines of output shows that gems will be installed in the folder XXX.

To find out where a particular gem is installed, use the gem which command. For example, gem which jekyll locates the Jekyll gem:

Источник