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 doctor
This reference was automatically generated from Bundler version 4.0.17.
bundle doctor [diagnose][--quiet] [--gemfile=GEMFILE] [--ssl]
bundle doctor ssl[--host=HOST] [--tls-version=TLS-VERSION] [--verify-mode=VERIFY-MODE]
bundle doctorhelp [COMMAND]
Description
You can diagnose common Bundler problems with this command such as checking gem environment or SSL/TLS issue.
Sub-commands
Diagnose (default Command)
Checks your Gemfile and gem environment for common problems. If issues are detected, Bundler prints them and exits status 1. Otherwise, Bundler prints a success message and exits status 0.
Examples of common problems caught include:
- Invalid Bundler settings
- Mismatched Ruby versions
- Mismatched platforms
- Uninstalled gems
- Missing dependencies
OPTIONS
--quiet- Only output warnings and errors.
--gemfile=GEMFILE- The location of the Gemfile(5) which Bundler should use. This defaults
to a Gemfile(5) in the current working directory. In general, Bundler
will assume that the location of the Gemfile(5) is also the project's
root and will try to find
Gemfile.lockandvendor/cacherelative to this location. --ssl- Diagnose common SSL problems when connecting to https://rubygems.org.
This flag runs the
bundle doctor sslsubcommand with default values underneath.
Ssl
If you've experienced issues related to SSL certificates and/or TLS versions while connecting to https://rubygems.org, this command can help troubleshoot common problems. The diagnostic will perform a few checks such as:
- Verify the Ruby OpenSSL version installed on your system.
- Check the OpenSSL library version used for compilation.
- Ensure CA certificates are correctly setup on your machine.
- Open a TLS connection and verify the outcome.
OPTIONS
--host=HOST- Perform the diagnostic on HOST. Defaults to
rubygems.org. --tls-version=TLS-VERSION- Specify the TLS version when opening the connection to HOST.
Accepted values are:
1.1or1.2. --verify-mode=VERIFY-MODE- Specify the TLS verify mode when opening the connection to HOST.
Defaults to
SSL_VERIFY_PEER.Accepted values are:
CLIENT_ONCE,FAIL_IF_NO_PEER_CERT,NONE,PEER.