Contents

BUNDLE-LOCK(1)							BUNDLE-LOCK(1)



NAME
       bundle-lock - Creates / Updates a lockfile without installing

SYNOPSIS
       bundle lock [--update] [--local] [--print] [--lockfile=PATH]

DESCRIPTION
       Lock the gems specified in Gemfile.

OPTIONS
       --update=<*gems>
	      Ignores  the  existing  lockfile. Resolve then updates lockfile.
	      Taking a list of gems or updating all gems if no list is	given.

       --local
	      Do not attempt to connect to rubygems.org. Instead, Bundler will
	      use the gems already present  in	Rubygems'  cache  or  in  ven-
	      dor/cache.  Note	that  if  a  appropriate platform-specific gem
	      exists on rubygems.org it will not be found.

       --print
	      Prints the lockfile to STDOUT instead of	writing  to  the  file
	      system.

       --lockfile=<path>
	      The path where the lockfile should be written to.

UPDATING ALL GEMS
       If  you	run  bundle  lock  with  --update option without list of gems,
       bundler will ignore any	previously  installed  gems  and  resolve  all
       dependencies  again  based on the latest versions of all gems available
       in the sources.

UPDATING A LIST OF GEMS
       Sometimes, you want to update a single gem in the Gemfile(5), and leave
       the  rest  of the gems that you specified locked to the versions in the
       Gemfile.lock.

       For instance, you  only	want  to  update  nokogiri,  run  bundle  lock
       --update nokogiri.

       Bundler will update nokogiri and any of its dependencies, but leave the
       rest of the gems that you specified locked to the versions in the  Gem-
       file.lock.



				 December 2015			BUNDLE-LOCK(1)

Version data entries

2 entries across 2 versions & 1 rubygems

Version	Path
bundler-1.12.0.rc	lib/bundler/man/bundle-lock.txt
bundler-1.11.0	lib/bundler/man/bundle-lock.txt