Bundle exec for isolated execution in Ruby - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does bundle exec do in Ruby?

bundle exec runs a Ruby command using the gems specified in your Gemfile.lock. It ensures your program uses the exact gem versions your project needs.

beginner

Why is bundle exec important for isolated execution?

It prevents conflicts by isolating your program's gem environment. This means your app won't accidentally use different gem versions installed globally on your system.

intermediate

How does bundle exec relate to the Gemfile.lock?

bundle exec uses the Gemfile.lock to know exactly which gem versions to load, ensuring consistency across different machines and environments.

beginner

What might happen if you run a Ruby script without bundle exec?

Your script might use wrong gem versions or gems not listed in your Gemfile. This can cause errors or unexpected behavior.

beginner

Give an example command using bundle exec to run a Ruby script named app.rb.

bundle exec ruby app.rb

This runs app.rb using the gems specified in your project.

What is the main purpose of bundle exec?

A To delete unused gems

B To run Ruby commands using the gems specified in the project

C To update Ruby to the latest version

D To install new gems globally

bundle exec runs commands using the gems listed in your Gemfile.lock, ensuring the right versions are used.

What file does bundle exec rely on to know which gem versions to use?

A Gemfile

B ruby_version.txt

C config.yml

D Gemfile.lock

bundle exec uses Gemfile.lock to lock gem versions for consistent execution.

What can happen if you run a Ruby script without bundle exec in a project with specific gem versions?

A The script might use wrong gem versions causing errors

B The script will run faster

C The script will ignore the Ruby version

D The script will automatically update gems

Without bundle exec, your script may use different gem versions than intended, leading to errors.

Which command correctly runs a Ruby script named app.rb using bundle exec?

A bundle exec ruby app.rb

B ruby bundle exec app.rb

C bundle install app.rb

D exec bundle ruby app.rb

The correct syntax is bundle exec ruby app.rb to run the script with the bundled gems.

Which of these is NOT a benefit of using bundle exec?

A Ensures consistent gem versions

B Prevents gem conflicts

C Automatically updates gems to latest versions

D Runs commands in isolated gem environment

bundle exec does not update gems; it uses the versions locked in Gemfile.lock.

Explain in your own words why bundle exec is used when running Ruby programs.

Think about how different projects might need different gem versions.

Describe what could go wrong if you forget to use bundle exec before running a Ruby script in a project.

Consider what happens if your program uses gems not intended for it.

Practice

1.

What is the main purpose of using bundle exec in a Ruby project?

easy

A. To create a new Ruby project with default settings

B. To update all gems to their latest versions globally

C. To uninstall unused gems from the system

D. To run commands using only the gems specified in the project's Gemfile

Solution

1. Step 1: Understand the role of bundle exec

   bundle exec runs commands using the gems listed in the project's Gemfile, isolating from other system gems.

2. Step 2: Compare options

   Options B, C, and D describe different gem or project management tasks unrelated to isolated execution.

3. Final Answer:

   To run commands using only the gems specified in the project's Gemfile -> Option D

4. Quick Check:

   bundle exec isolates gems = A [OK]

Hint: Remember: bundle exec uses project gems only, avoiding conflicts [OK]

Common Mistakes:

• Thinking bundle exec updates gems
• Confusing bundle exec with gem uninstall
• Assuming bundle exec creates projects

2.

Which of the following is the correct syntax to run a Ruby script app.rb using bundle exec?

easy

A. bundle exec ruby app.rb

B. ruby bundle exec app.rb

C. bundle ruby exec app.rb

D. exec bundle ruby app.rb

Solution

1. Step 1: Recall correct command order

   The correct syntax places bundle exec before the command to run, here ruby app.rb.

2. Step 2: Validate options

   Only bundle exec ruby app.rb correctly places bundle exec before ruby app.rb. Others mix order incorrectly.

3. Final Answer:

   bundle exec ruby app.rb -> Option A

4. Quick Check:

   bundle exec before command = C [OK]

Hint: Put 'bundle exec' right before the command you want to run [OK]

Common Mistakes:

• Swapping order of bundle exec and ruby
• Inserting exec or bundle in wrong places
• Omitting bundle exec entirely

3.

Given a Ruby project with a Gemfile specifying rspec version 3.10.0, what will be the output of running rspec --version vs bundle exec rspec --version if the system has rspec 4.0.0 installed globally?

medium

A. rspec --version shows 4.0.0, bundle exec rspec --version shows 3.10.0

B. rspec --version shows 3.10.0, bundle exec rspec --version shows 4.0.0

C. Both commands show 4.0.0

D. Both commands show 3.10.0

Solution

1. Step 1: Understand gem version usage

   Running rspec --version uses the system's global gem version, which is 4.0.0 here.

2. Step 2: Effect of bundle exec

   bundle exec rspec --version runs using the project's Gemfile version, 3.10.0, isolating from global gems.

3. Final Answer:

   rspec --version shows 4.0.0, bundle exec rspec --version shows 3.10.0 -> Option A

4. Quick Check:

   bundle exec uses Gemfile version = D [OK]

Hint: Without bundle exec uses global gems; with it uses project gems [OK]

Common Mistakes:

• Assuming both commands show same version
• Confusing global and project gem versions
• Ignoring Gemfile gem isolation

4.

Consider this command run inside a Ruby project folder:
rspec spec/test_spec.rb
The test fails due to a gem version conflict. How can you fix this using bundle exec?

medium

A. Run gem install rspec to update the gem globally

B. Run bundle exec rspec spec/test_spec.rb to use project gems

C. Run rspec --update to fix conflicts automatically

D. Delete the Gemfile and try again

Solution

1. Step 1: Identify cause of failure

   Failure is due to gem version conflict between global and project gems.

2. Step 2: Use bundle exec to isolate gems

   Running bundle exec rspec spec/test_spec.rb forces use of project Gemfile gems, resolving conflicts.

3. Final Answer:

   Run bundle exec rspec spec/test_spec.rb to use project gems -> Option B

4. Quick Check:

   bundle exec fixes gem conflicts = A [OK]

Hint: Use bundle exec before commands to fix gem conflicts [OK]

Common Mistakes:

• Trying to update gems globally instead of isolating
• Using invalid rspec options
• Deleting Gemfile which breaks project setup

5.

You have a Ruby project with multiple gems and versions specified in the Gemfile. You want to run a custom Ruby script script.rb that depends on these gems. Which command ensures your script uses the correct gem versions and avoids conflicts?

hard

A. ruby script.rb

B. gem install script.rb

C. bundle exec ruby script.rb

D. bundle install script.rb

Solution

1. Step 1: Understand gem version isolation need

   Running ruby script.rb alone may use system gems, causing version conflicts.

2. Step 2: Use bundle exec to run script with project gems

   bundle exec ruby script.rb runs the script using gems specified in the Gemfile, ensuring correct versions.

3. Step 3: Eliminate incorrect options

   gem install script.rb and bundle install script.rb are invalid commands for running scripts.

4. Final Answer:

   bundle exec ruby script.rb -> Option C

5. Quick Check:

   Use bundle exec to run scripts with project gems = B [OK]

Hint: Always prefix scripts with bundle exec to use project gems [OK]

Common Mistakes:

• Running scripts without bundle exec causing conflicts
• Confusing gem install with running scripts
• Trying to bundle install a script file