Bird
Raised Fist0
Rubyprogramming~30 mins

Gemfile for project dependencies in Ruby - Mini Project: Build & Apply

Choose your learning style10 modes available
Gemfile for project dependencies
📖 Scenario: You are starting a new Ruby project and need to manage the libraries (called gems) your project will use. Ruby uses a file named Gemfile to list these dependencies so they can be installed easily.
🎯 Goal: Create a Gemfile that lists specific gems your project needs, then add a Ruby version requirement, and finally print the list of gems to confirm your setup.
📋 What You'll Learn
Create a Gemfile with exact gem entries
Add a Ruby version requirement in the Gemfile
Use Ruby code to read and print the gem names from the Gemfile
💡 Why This Matters
🌍 Real World
Managing project dependencies with a Gemfile is essential for Ruby projects to ensure consistent environments and easy setup.
💼 Career
Ruby developers and DevOps engineers use Gemfiles daily to manage libraries and maintain project stability.
Progress0 / 4 steps
1
Create a Gemfile with gems
Create a file named Gemfile and add these exact gem entries:
gem 'rails', '7.0.4', gem 'puma', '5.6.4', and gem 'nokogiri', '1.14.4'.
Ruby
Hint

Start your Gemfile with source 'https://rubygems.org' then add each gem line exactly as shown.

2
Add Ruby version requirement
Add the exact line ruby '3.2.2' at the top of the Gemfile to specify the Ruby version your project uses.
Ruby
Hint

The Ruby version line should be the very first line in the Gemfile.

3
Read gem names from Gemfile
Write Ruby code that reads the Gemfile and creates a list called gem_names containing only the gem names as strings (e.g., 'rails', 'puma', 'nokogiri'). Use File.readlines('Gemfile') and string methods to extract the names.
Ruby
Hint

Use map to transform lines and compact to remove nil values.

4
Print the list of gem names
Write a puts statement to print the gem_names list so the output shows:
["rails", "puma", "nokogiri"]
Ruby
Hint

Use puts gem_names.inspect to print the array as shown.

Practice

(1/5)
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
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard