If you’re on a Mac and using RVM (as you should be :) ), just leave sudo off. One more note about installing gems: you might notice that a gem’s documentation tells you to use sudo when installing it. There may be some arguments you should add to that command however, in most cases, that should get you through.

It’s important to pay attention to the documentation for the gem, though. Once you find the gem, install it like this: gem install GEM_NAME The hard part is finding the gem you’d like to use often, you can just google for whatever functionality you’re looking for. How do you do this? Again, it’s pretty simple. So, now that you’ve got the RubyGems library installed, you can use it to install whatever gems you please. I should mention that if you’re on Windows and installed Ruby via the RubyInstaller, you do have RubyGems installed. If you’d like to upgrade, run gem update -system. If you think you might already have RubyGems installed, run gem -v to get the version number. Just head over to the RubyGems download page, download the TAR or ZIP, open it up, and run ruby setup.rb in the terminal from that folder You might need admin privileges to do this ( sudo on unix systems, start the command line with 'Run as Administrator' on Windows). If you’ve decided to stick with Ruby 1.8.*, it’s not too hard to install. If you’re on Ruby 1.9.* (what we’re using in this series), then you don’t have to worry about installing RubyGems it’s built in. Of course, you’ll need Ruby installed first, but you should have that by now. That’s just a few of the things you can do with gems.īefore we can install and use gems we need to install the RubyGems library.

If that sounds vague, here are some practical problems that gems solve: It’s some functionality that you’ll install to fill a specific need. You can think of a Ruby Gem as a library or plug-in.

Use ruby in visual studio code tutorial