Guides
Getting Started
Guides
Dependency Management
- How to manage application dependencies with Bundler
- How to manage dependencies with Bundler
- How to update gems with Bundler
- How to manage groups of gems
- How to install gems from git repositories
- Recommended Workflow with Version Control
- How to use Bundler with Ruby
- How to use Bundler in a single-file Ruby script
- How to deploy bundled applications
Gem Development
Publishing & Security
- Trusted Publishing
- Setting up multi-factor authentication
- Using multi-factor authentication in command line
- MFA requirement opt in
- Managing owners using UI
- Organizations
- Removing a Published gem
- Security Practices
Integrations
- How to use Bundler with Rails
- How to use Bundler with Sinatra
- How to use Bundler with Docker
- How to use Bundler with RubyMotion
Hosting & Sources
Extending
Troubleshooting
- How to troubleshoot RubyGems and Bundler TLS/SSL Issues
- SSL Certificate Update
- How to use git bisect with Bundler
Concepts
Reference
- gem Command Reference
- Bundler Command Reference
- Gemfile Reference
- Ruby Directive
- Specification Reference
- RubyGems.org API
- RubyGems.org API V2.0
- RubyGems.org Compact Index API
- RubyGems.org rate limits
- API key scopes
- Bundler compatibility with Ruby
- Known Bundler Plugins
Appendix
bundle
Ruby Dependency Management
This reference was automatically generated from Bundler version 4.0.17.
bundle COMMAND [--no-color] [--verbose] [ARGS]
Description
Bundler manages an application's dependencies through its entire life
across many machines systematically and repeatably.
See the bundler website for information on getting
started, and Gemfile(5) for more information on the Gemfile format.
Options
--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 information
Bundle Commands
We divide bundle subcommands into primary commands and utilities:
Primary Commands
bundle install(1)- Install the gems specified by the
GemfileorGemfile.lock bundle update(1)- Update dependencies to their latest versions
bundle cache(1)- Package the .gem files required by your application into the
vendor/cachedirectory (aliases:bundle package,bundle pack) bundle exec(1)- Execute a script in the current bundle
bundle config(1)- Specify and read configuration options for Bundler
bundle help(1)- Display detailed help for each subcommand
Utilities
bundle add(1)- Add the named gem to the Gemfile and run
bundle install bundle binstubs(1)- Generate binstubs for executables in a gem
bundle check(1)- Determine whether the requirements for your application are installed and available to Bundler
bundle show(1)- Show the source location of a particular gem in the bundle
bundle info(1)- Show information for the given gem in your bundle
bundle list(1)- List all the gems in the bundle
bundle licenses(1)- Print the license of all gems in the bundle
bundle fund(1)- Lists information about gems seeking funding assistance
bundle outdated(1)- Show all of the outdated gems in the current bundle
-
bundle console(1)(deprecated) - Start an IRB session in the current bundle
bundle open(1)- Open an installed gem in the editor
bundle lock(1)- Generate a lockfile for your dependencies
bundle init(1)- Generate a simple
Gemfile, placed in the current directory bundle gem(1)- Create a simple gem, suitable for development with Bundler
bundle platform(1)- Display platform compatibility information
bundle clean(1)- Clean up unused gems in your Bundler directory
bundle pristine(1)- Restores installed gems to their pristine condition
bundle doctor(1)- Display warnings about common problems
bundle env(1)- Print information about the environment Bundler is running under
bundle issue(1)- Get help reporting Bundler issues
bundle remove(1)- Removes gems from the Gemfile
bundle plugin(1)- Manage Bundler plugins
bundle version(1)- Prints Bundler version information
Plugins
When 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.