Why gem management matters in Ruby

Introduction

Gem management helps you keep track of the extra tools (gems) your Ruby program needs. It makes sure your program works the same way on any computer.

When you want to add new features to your Ruby program using external gems.

When you share your Ruby project with others and want them to install the right gems easily.

When you update gems and want to avoid breaking your program.

When you work on multiple Ruby projects that need different versions of the same gem.

Syntax

Ruby

gem 'gem_name', '~> version_number'

# Example in a Gemfile:
gem 'rails', '~> 7.0.0'

A Gemfile lists all the gems your project needs.

The ~> symbol means 'compatible with this version'.

Examples

This means use Nokogiri gem version 1.13.x, but not 1.14 or higher.

Ruby

gem 'nokogiri', '~> 1.13.0'

This installs the latest version of the RSpec gem.

Ruby

gem 'rspec'

This installs exactly version 5.6.4 of the Puma gem.

Ruby

gem 'puma', '5.6.4'

Sample Program

This example shows a Gemfile listing the 'colorize' gem with a version rule. After running bundle install, the Ruby script uses the gem to print green text.

Ruby

# Gemfile
source 'https://rubygems.org'
gem 'colorize', '~> 0.8.1'

# Run 'bundle install' in terminal to install gems

# example.rb
require 'colorize'

puts 'Hello, world!'.colorize(:green)

Important Notes

Always use a Gemfile to list gems for your project.

Run bundle install to install all gems listed in the Gemfile.

Gem management avoids conflicts when different projects need different gem versions.

Summary

Gem management keeps your Ruby projects organized and working smoothly.

It helps you share your project with others easily.

Using a Gemfile and Bundler is the standard way to manage gems.