bundle - Ruby Dependency Management
| Use Case | Command | Description |
|---|---|---|
| Install gems from Gemfile | bundle install | 📦 Install the gems specified by the Gemfile or Gemfile.lock |
| Update dependencies | bundle update | 🔄 Update dependencies to their latest versions |
| Execute script in bundle context | bundle exec | ⚡ Execute a script in the current bundle |
| Add a new gem | bundle add | ✨ Add the named gem to the Gemfile and run bundle install |
| Show outdated gems | bundle outdated | 📅 Show all of the outdated gems in the current bundle |
| Generate binstubs | bundle binstubs | 🔧 Generate binstubs for executables in a gem |
| Check gem compatibility | bundle check | ✅ Determine whether requirements are installed and available |
| Show gem source location | bundle show | 📍 Show the source location of a particular gem |
| Open gem in editor | bundle open | ✏️ Open an installed gem in the editor |
| Generate lockfile | bundle lock | 🔒 Generate a lockfile for your dependencies |
bundle COMMAND [--no-color] [--verbose] [ARGS]
Bundler manages an application's dependencies through its entire life across many machines systematically and repeatably.
See the bundler website https://bundler.io for information on getting started, and Gemfile(5) for more information on the Gemfile format.
--no-color 🎨 — Print all output without color--retry, -r 🔄 — Specify the number of times you wish to attempt network commands--verbose, -V 📝 — Print out additional logging informationWe divide bundle subcommands into primary commands and utilities:
bundle install — Install the gems specified by the Gemfile or Gemfile.lockbundle update — Update dependencies to their latest versionsbundle package — Package the .gem files required by your application into the vendor/cache directorybundle exec — Execute a script in the current bundlebundle config — Specify and read configuration options for Bundlerbundle help — Display detailed help for each subcommandbundle add — Add the named gem to the Gemfile and run bundle installbundle binstubs — Generate binstubs for executables in a gembundle check — Determine whether the requirements for your application are installed and available to Bundlerbundle show — Show the source location of a particular gem in the bundlebundle outdated — Show all of the outdated gems in the current bundlebundle console — Start an IRB session in the current bundlebundle open — Open an installed gem in the editorbundle lock — Generate a lockfile for your dependenciesbundle viz — Generate a visual representation of your dependenciesbundle init — Generate a simple Gemfile, placed in the current directorybundle gem — Create a simple gem, suitable for development with Bundlerbundle platform — Display platform compatibility informationbundle clean — Clean up unused gems in your Bundler directorybundle doctor — Display warnings about common problemsbundle remove — Removes gems from the GemfileWhen running 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.
These commands are obsolete and should no longer be used:
December 2021 — BUNDLE(1)
Generated by phpman v4.9.26-5-g7740029 Author: Che Dong Under GNU General Public License
2026-08-14 20:28 @2600:1f28:365:80b0:4d23:66fa:c2bb:7bae
CrawledBy CCBot/2.0 (https://commoncrawl.org/faq/)