BUNDLE(1)

📦
version 4.0.20 · 10 versions
, in fedora 44, ubuntu stonking

💖 BUNDLE(1) — the manual, but make it slay 💖

okay bestie, so this is bundle, living in the General Commands Manual section of your man pages, and it's literally the whole ✨Ruby Dependency Management✨ situation. sit down, grab a boba, we're doing this 🧋

🌸 NAME 🌸

bundle — Ruby Dependency Management. that's it. that's the girl. 💅

✨ SYNOPSIS ✨

bundle COMMAND [--no-color] [--verbose] [ARGS]

like… you pick a COMMAND, you toss in some flags, you pass ARGS. iconic behaviour fr fr 🫶

🦋 DESCRIPTION 🦋

Bundler manages an application's dependencies through its entire life, across many machines, systematically and repeatably. not chaotic. not one-off. systematic. repeatable. main character energy only 💁‍♀️

if you're just getting started, go read the RubyGems guides at https://guides.rubygems.org/, and for the whole tea on the Gemfile format, check out Gemfile(5). no cap, they'll help 🎀

👑 OPTIONS 👑

  • --no-color — prints ALL the output with zero color. plain. monochrome. no rainbow 😭
  • --retry, -r — tells it how many times you wanna attempt network commands. you pick the number 🔁
  • --verbose, -V — prints out additional logging information. more words, more insight, we love a chatty queen 🗣️

🌈 BUNDLE COMMANDS 🌈

so we split the bundle subcommands into two lil categories: primary commands and utilities. think varsity squad vs. the supporting cast that honestly carries the whole show 🎬

💜 PRIMARY COMMANDS 💜

  • bundle install(1) bundle-install.1.html — installs the gems specified by the Gemfile or Gemfile.lock. the classic. the moment. 🔥
  • bundle update(1) bundle-update.1.html — updates dependencies to their latest versions. glow-up time ✨
  • bundle cache(1) bundle-cache.1.html — packages the .gem files your app needs into the vendor/cache directory (aliases: bundle package, bundle pack) 📦
  • bundle exec(1) bundle-exec.1.html — executes a script in the current bundle 🏃‍♀️
  • bundle config(1) bundle-config.1.html — specifies and reads configuration options for Bundler ⚙️
  • bundle help(1) bundle-help.1.html — displays detailed help for each subcommand. the girl who always knows where the info lives 🙋‍♀️

🍓 UTILITIES 🍓

  • bundle add(1) bundle-add.1.html — adds the named gem to the Gemfile and runs bundle install ➕
  • bundle binstubs(1) bundle-binstubs.1.html — generates binstubs for executables in a gem 🌱
  • bundle check(1) bundle-check.1.html — determines whether the requirements for your application are installed and available to Bundler ✅
  • bundle show(1) bundle-show.1.html — shows the source location of a particular gem in the bundle 📍
  • bundle info(1) bundle-info.1.html — shows information for the given gem in your bundle 🔍
  • bundle list(1) bundle-list.1.html — lists all the gems in the bundle 📋
  • bundle licenses(1) bundle-licenses.1.html — prints the license of all gems in the bundle 📜
  • bundle fund(1) bundle-fund.1.html — lists information about gems seeking funding assistance. support the devs bestie 💸
  • bundle outdated(1) bundle-outdated.1.html — shows all of the outdated gems in the current bundle 🕰️
  • bundle console(1) (deprecated) — starts an IRB session in the current bundle. ⚠️ deprecated, so don't get too attached, she's on her way out ⚠️
  • bundle open(1) bundle-open.1.html — opens an installed gem in the editor 📂
  • bundle lock(1) bundle-lock.1.html — generates a lockfile for your dependencies 🔒
  • bundle init(1) bundle-init.1.html — generates a simple Gemfile, placed in the current directory 🐣
  • bundle gem(1) bundle-gem.1.html — creates a simple gem, suitable for development with Bundler 💎
  • bundle platform(1) bundle-platform.1.html — displays platform compatibility information 🖥️
  • bundle clean(1) bundle-clean.1.html — cleans up unused gems in your Bundler directory 🧹
  • bundle pristine(1) bundle-pristine.1.html — restores installed gems to their pristine condition 🧼
  • bundle doctor(1) bundle-doctor.1.html — displays warnings about common problems 🩺
  • bundle env(1) bundle-env.1.html — prints information about the environment Bundler is running under 🌍
  • bundle issue(1) bundle-issue.1.html — get help reporting Bundler issues 🐛
  • bundle remove(1) bundle-remove.1.html — removes gems from the Gemfile 🗑️
  • bundle plugin(1) bundle-plugin.1.html — manages Bundler plugins 🔌
  • bundle version(1) bundle-version.1.html — prints Bundler version information 🏷️

🧚 PLUGINS 🧚

so here's the cute part: when you run a command that isn't listed in PRIMARY COMMANDS or UTILITIES, Bundler will try to find an executable on your path named bundler-<command> and execute it — passing down any extra arguments to it 🫶

basically, if bundle doesn't recognize the vibe, it goes looking for your plugin. mystery solved, detective 🕵️‍♀️

and that's the whole page bestie, you ate it 💅✨ this was BUNDLE(1) from the General Commands Manual, dated April 2026, and if you made it all the way down here you are lowkey a legend 👑 mwah, go install your gems 💖🦋🌸

📦 where this page comes from