1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2022-11-09 12:17:21 -05:00
ruby--ruby/man/bundle.ronn
hsbt 59c8d50653 Added bundler as default gems. Revisit [Feature #12733]
* bin/*, lib/bundler/*, lib/bundler.rb, spec/bundler, man/*:
    Merge from latest stable branch of bundler/bundler repository and
    added workaround patches. I will backport them into upstream.
  * common.mk, defs/gmake.mk: Added `test-bundler` task for test suite
    of bundler.
  * tool/sync_default_gems.rb: Added sync task for bundler.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65509 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-02 23:07:56 +00:00

108 lines
3 KiB
Markdown

bundle(1) -- Ruby Dependency Management
=======================================
## SYNOPSIS
`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](http://bundler.io) 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)`](bundle-install.1.html):
Install the gems specified by the `Gemfile` or `Gemfile.lock`
* [`bundle update(1)`](bundle-update.1.html):
Update dependencies to their latest versions
* [`bundle package(1)`](bundle-package.1.html):
Package the .gem files required by your application into the
`vendor/cache` directory
* [`bundle exec(1)`](bundle-exec.1.html):
Execute a script in the current bundle
* [`bundle config(1)`](bundle-config.1.html):
Specify and read configuration options for Bundler
* `bundle help(1)`:
Display detailed help for each subcommand
## UTILITIES
* [`bundle add(1)`](bundle-add.1.html):
Add the named gem to the Gemfile and run `bundle install`
* [`bundle binstubs(1)`](bundle-binstubs.1.html):
Generate binstubs for executables in a gem
* [`bundle check(1)`](bundle-check.1.html):
Determine whether the requirements for your application are installed
and available to Bundler
* [`bundle show(1)`](bundle-show.1.html):
Show the source location of a particular gem in the bundle
* [`bundle outdated(1)`](bundle-outdated.1.html):
Show all of the outdated gems in the current bundle
* `bundle console(1)`:
Start an IRB session in the current bundle
* [`bundle open(1)`](bundle-open.1.html):
Open an installed gem in the editor
* [`bundle lock(1)`](bundle-lock.1.hmtl):
Generate a lockfile for your dependencies
* [`bundle viz(1)`](bundle-viz.1.html):
Generate a visual representation of your dependencies
* [`bundle init(1)`](bundle-init.1.html):
Generate a simple `Gemfile`, placed in the current directory
* [`bundle gem(1)`](bundle-gem.1.html):
Create a simple gem, suitable for development with Bundler
* [`bundle platform(1)`](bundle-platform.1.html):
Display platform compatibility information
* [`bundle clean(1)`](bundle-clean.1.html):
Clean up unused gems in your Bundler directory
* [`bundle doctor(1)`](bundle-doctor.1.html):
Display warnings about common problems
## 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.
## OBSOLETE
These commands are obsolete and should no longer be used:
* `bundle cache(1)`
* `bundle show(1)`