Bundle exec for isolated execution in Ruby

Introduction

Bundle exec helps run Ruby commands using the exact gems your project needs. It keeps your project safe from conflicts with other versions.

When you want to run a Ruby script using the gems listed in your project's Gemfile.

When you want to avoid errors caused by different gem versions installed on your system.

When you want to make sure your project runs the same way on different computers.

When you want to run commands like rails, rake, or rspec with the correct gem versions.

Syntax

Ruby

bundle exec <command> [arguments]

bundle exec runs the command using gems from your Gemfile.lock.

You put the command you want to run after bundle exec.

Examples

This runs the Rails server using the gems specified in your project.

Ruby

bundle exec rails server

This runs the RSpec tests for the user model using the correct gem versions.

Ruby

bundle exec rspec spec/models/user_spec.rb

This runs the database migration task safely with the right gems.

Ruby

bundle exec rake db:migrate

Sample Program

This program prints 'Hello, world!' in green color using the colorize gem. Using bundle exec ensures it uses the gem version from your Gemfile.

Ruby

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

# Then run:
# bundle install

# Now create a Ruby file named example.rb:
require 'colorize'

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

# Run this with:
# bundle exec ruby example.rb

Important Notes

If you don't use bundle exec, your system might use a different gem version and cause errors.

You need to run bundle install first to create the Gemfile.lock file.

Using bundle exec helps keep your project consistent and easy to share.

Summary

bundle exec runs commands using your project's gems only.

It prevents conflicts from different gem versions on your computer.

Always use it when running Ruby commands in a project with a Gemfile.