1BUNDLE-BINSTUBS(1)                                          BUNDLE-BINSTUBS(1)
2
3
4

NAME

6       bundle-binstubs - Install the binstubs of the listed gems
7

SYNOPSIS

9       bundle binstubs GEM_NAME [--force] [--path PATH] [--standalone]
10

DESCRIPTION

12       Binstubs  are  scripts  that wrap aroung executables. Bundler creates a
13       small Ruby file (a binstub) that loads Bundler, runs the  command,  and
14       puts  it  into  bin/. Binstubs are a shortcut-or alternative- to always
15       using bundle exec. This gives you a file that can by run directly,  and
16       one  that  will always run the correct gem version used by the applica‐
17       tion.
18
19       For example, if you run bundle binstubs rspec-core, Bundler will create
20       the file bin/rspec. That file will contain enough code to load Bundler,
21       tell it to load the bundled gems, and then run rspec.
22
23       This command generates binstubs for executables in  GEM_NAME.  Binstubs
24       are  put into bin, or the --path directory if one has been set. Calling
25       binstubs with [GEM [GEM]] will create binstubs for all given gems.
26

OPTIONS

28       --force
29              Overwrite existing binstubs if they exist.
30
31       --path The location to install the specified binstubs to. This defaults
32              to bin.
33
34       --standalone
35              Makes  binstubs  that  can work without depending on Rubygems or
36              Bundler at runtime.
37
38       --sheband
39              Specify a different shebang executable  name  than  the  default
40              (default ´ruby´)
41

BUNDLE INSTALL --BINSTUBS

43       To  create  binstubs  for  all  the  gems in the bundle you can use the
44       --binstubs flag in [bundle install(1)][bundle-install].
45
46
47
48                                 October 2017               BUNDLE-BINSTUBS(1)