Gemfile for project dependencies in Ruby - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Gemfile in a Ruby project?

A Gemfile is a file that lists all the Ruby gems (libraries) your project needs. It helps manage and install these dependencies easily.

beginner

How do you specify a gem and its version in a Gemfile?

You write: gem 'gem_name', '~> version_number'. For example, gem 'rails', '~> 7.0' means use Rails version 7.0 or compatible updates.

beginner

What command do you run to install gems listed in the Gemfile?

You run bundle install. This reads the Gemfile and installs all the listed gems.

beginner

What is the purpose of the source line in a Gemfile?

The source line tells Bundler where to find gems, usually https://rubygems.org, the main Ruby gem repository.

intermediate

How can you group gems for specific environments in a Gemfile?

You use group :environment_name do ... end. For example, group :development do gem 'pry' end means the gem is only for development.

What does the command bundle install do?

A Installs all gems listed in the Gemfile

B Creates a new Gemfile

C Removes unused gems

D Updates Ruby version

bundle install reads the Gemfile and installs all the gems your project needs.

How do you specify the source for gems in a Gemfile?

A install source 'https://rubygems.org'

B gem 'source', 'https://rubygems.org'

C use 'https://rubygems.org'

D source 'https://rubygems.org'

The source line at the top of the Gemfile tells Bundler where to find gems.

Which syntax correctly adds the gem 'rails' version 7.0 or higher but less than 8.0?

A gem 'rails', '~> 7.0'

B gem 'rails', '>= 7.0'

C gem 'rails', '= 7.0'

D gem 'rails', '< 7.0'

The ~> operator means compatible with version 7.0, but less than 8.0.

How do you add gems only for the development environment?

A gem 'pry', environment: 'development'

B group :development do gem 'pry' end

C if environment == 'development' gem 'pry' end

D gem 'pry' only: :development

Using group :development do ... end wraps gems for that environment.

What file does Bundler create to lock gem versions after installing?

A gems.locked

B Gemfile.txt

C Gemfile.lock

D bundle.lock

Bundler creates Gemfile.lock to record exact gem versions installed.

Explain the purpose of a Gemfile and how it helps manage project dependencies.

Think about how you tell your project what tools it needs.

Describe how to group gems for different environments in a Gemfile and why this is useful.

Consider when you want some tools only during development.

Practice

1. What is the main purpose of a Gemfile in a Ruby project?

easy

A. To configure the web server

B. To write Ruby program logic

C. To store database credentials

D. To list all the gems the project depends on

Solution

1. Step 1: Understand the role of Gemfile

   A Gemfile is used to specify which gems (libraries) a Ruby project needs to work properly.

2. Step 2: Compare options with Gemfile purpose

   Only To list all the gems the project depends on correctly states that Gemfile lists project gem dependencies.

3. Final Answer:

   To list all the gems the project depends on -> Option D

4. Quick Check:

   Gemfile purpose = list gems [OK]

Hint: Gemfile lists gems needed for the project [OK]

Common Mistakes:

• Confusing Gemfile with Ruby code files
• Thinking Gemfile stores secrets or configs
• Assuming Gemfile runs the program

2. Which line is the correct syntax to add the gem 'rails' version 7.0.0 in a Gemfile?

easy

A. gem 'rails', '7.0.0'

B. gem rails, '7.0.0'

C. gem 'rails' version '7.0.0'

D. gem 'rails' => '7.0.0'

Solution

1. Step 1: Recall Gemfile gem syntax

   The correct syntax uses the keyword gem, gem name in quotes, then version as a string separated by a comma.

2. Step 2: Check each option

   gem 'rails', '7.0.0' matches the correct syntax: gem 'rails', '7.0.0'. Others have syntax errors or wrong keywords.

3. Final Answer:

   gem 'rails', '7.0.0' -> Option A

4. Quick Check:

   Gemfile gem syntax = gem 'name', 'version' [OK]

Hint: Use gem 'name', 'version' format in Gemfile [OK]

Common Mistakes:

• Omitting quotes around gem name
• Using => instead of comma for version
• Writing version without quotes

3. Given this Gemfile snippet:

source 'https://rubygems.org'
gem 'nokogiri', '~> 1.12.0'
gem 'puma', '5.0'

What happens when you run bundle install?

medium

A. Installs latest versions of nokogiri and puma

B. Installs nokogiri version exactly 1.12.0 and puma latest version

C. Installs nokogiri version 1.12.x and puma version 5.0

D. Throws an error due to invalid version syntax

Solution

1. Step 1: Understand version specifiers in Gemfile

   ~> 1.12.0 means any version >=1.12.0 and <1.13.0 (patch updates allowed). '5.0' means exactly version 5.0.

2. Step 2: Interpret bundle install behavior

   Bundle installs nokogiri in 1.12.x range and puma exactly 5.0, matching Installs nokogiri version 1.12.x and puma version 5.0.

3. Final Answer:

   Installs nokogiri version 1.12.x and puma version 5.0 -> Option C

4. Quick Check:

   ~> means compatible version, exact string means exact version [OK]

Hint: ~> means compatible version, exact string means exact version [OK]

Common Mistakes:

• Thinking '~>' means exact version
• Assuming '5.0' means latest version
• Confusing version operators

4. Identify the error in this Gemfile snippet:

source 'https://rubygems.org'
gem 'rails', '6.1.4'
gem 'pg', '~> 1.2.3'
gem 'puma' '5.0'

medium

A. Missing comma between gem name and version in last line

B. Incorrect source URL

C. Version numbers are invalid

D. Gem 'pg' version specifier is wrong

Solution

1. Step 1: Check syntax of each gem line

   Each gem line should have a comma between gem name and version string.

2. Step 2: Locate the error

   Last line has gem 'puma' '5.0' missing a comma between 'puma' and '5.0'.

3. Final Answer:

   Missing comma between gem name and version in last line -> Option A

4. Quick Check:

   Gemfile gem syntax requires comma [OK]

Hint: Check commas between gem name and version [OK]

Common Mistakes:

• Omitting commas between gem name and version
• Assuming source URL is incorrect
• Misreading version specifiers

5. You want to add a gem only for the development environment in your Gemfile. Which is the correct way to do this?

hard

A. gem 'pry', environment: 'development'

B. group :development do
gem 'pry'
end

C. gem 'pry' if ENV['RACK_ENV'] == 'development'

D. group 'development' gem 'pry' end

Solution

1. Step 1: Recall how to specify environment groups in Gemfile

   Use group :environment_name do ... end block to add gems for specific environments.

2. Step 2: Evaluate each option

   group :development do gem 'pry' end correctly uses group :development do ... end syntax. Others are invalid Ruby or Gemfile syntax.

3. Final Answer:

   group :development do gem 'pry' end -> Option B

4. Quick Check:

   Use group blocks for environment-specific gems [OK]

Hint: Use group :env do ... end for environment gems [OK]

Common Mistakes:

• Trying to add environment as gem option
• Using if conditions inside Gemfile
• Incorrect group block syntax