Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   9211 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

BUNDLE(1)							     BUNDLE(1)

NAME
       bundle - 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

       --verbose
	      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 context of 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)
	      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 outdated(1)][bundle-outdated]
	      Show all of the outdated gems in the current bundle

       bundle console(1)
	      Start an IRB session in the context of the current bundle

       bundle open(1)
	      Open an installed gem in the editor

       [bundle lock(1)][bundle-lock]
	      Generate a lockfile for your dependencies

       bundle viz(1)
	      Generate a visual representation of your dependencies

       bundle init(1)
	      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)
	      Clean up unused gems in your bundler directory

       bundle doctor(1)
	      Display warnings about common potential problems

PLUGINS
       When  running a command that isn´t listed in PRIMARY COMMANDS or UTILI‐
       TIES, Bundler will try  to  find	 an  executable	 on  your  path	 named
       bundler-<command>  and  execute it, passing down any extra arguments to
       it.

BUNDLER TRAMPOLINING
       Bundler includes a feature called trampolining,	designed  to  allow  a
       single  developer  to  work  on	multiple  projects,  each on different
       Bundler versions. The trampoline will  infer  the  correct  version  of
       Bundler	to  use	 for each project and load that version instead of the
       version directly invoked (which is almost  always  the  newest  version
       installed locally).

       Bundler	by  default will use the Bundler version in the current direc‐
       tory to determine the version to trampoline to, reading from  the  BUN‐
       DLED WITH section. However, if the BUNDLER_VERSION environment variable
       is set, that version will override the lockfile inference  and  can  be
       used in directories without a lockfile.

       Until the target version is Bundler 2 or later, BUNDLE_TRAMPOLINE_FORCE
       must be set for the trampoline to be used. Additionally, BUNDLE_TRAMPO‐
       LINE_DISABLE can be set to completely disable the trampoline.

OBSOLETE
       These commands are obsolete and should no longer be used

       ·   bundle cache(1)

       ·   bundle list(1)

				   July 2017			     BUNDLE(1)

Vote for polarhome