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

NAME

6       bundle-package - Package your needed .gem files into your application
7

SYNOPSIS

9       bundle package
10

DESCRIPTION

12       Copy  all of the .gem files needed to run the application into the ven‐
13       dor/cache directory. In the future, when running bundle install(1) bun‐
14       dle-install.1.html, use the gems in the cache in preference to the ones
15       on rubygems.org.
16

GIT AND PATH GEMS

18       Since Bundler 1.2, the bundle package command can also package :git and
19       :path  dependencies  besides  .gem  files.  This needs to be explicitly
20       enabled via the --all option. Once  used,  the  --all  option  will  be
21       remembered.
22

REMOTE FETCHING

24       By  default,  if you simply run bundle install(1) bundle-install.1.html
25       after running bundle  package(1)  bundle-package.1.html,  bundler  will
26       still  connect to rubygems.org to check whether a platform-specific gem
27       exists for any of the gems in vendor/cache.
28
29       For instance, consider this Gemfile(5):
30
31
32
33           source "https://rubygems.org"
34
35           gem "nokogiri"
36
37
38
39       If you run bundle package under C Ruby, bundler will retrieve the  ver‐
40       sion  of  nokogiri  for the "ruby" platform. If you deploy to JRuby and
41       run bundle install, bundler is forced to check to see whether a  "java"
42       platformed nokogiri exists.
43
44       Even  though  the  nokogiri  gem  for  the Ruby platform is technically
45       acceptable on JRuby, it actually has a C extension that does not run on
46       JRuby.  As  a  result,  bundler  will,  by  default,  still  connect to
47       rubygems.org to check whether it has a version of one of your gems more
48       specific to your platform.
49
50       This problem is also not just limited to the "java" platform. A similar
51       (common) problem can happen when developing on Windows and deploying to
52       Linux, or even when developing on OSX and deploying to Linux.
53
54       If  you know for sure that the gems packaged in vendor/cache are appro‐
55       priate for the platform you are on, you can run bundle install  --local
56       to  skip  checking  for more appropriate gems, and just use the ones in
57       vendor/cache.
58
59       One way to be sure that you have the right platformed versions  of  all
60       your gems is to run bundle package on an identical machine and check in
61       the gems. For instance, you can run  bundle  package  on  an  identical
62       staging  box during your staging process, and check in the vendor/cache
63       before deploying to production.
64
65
66
67                                   July 2014                 BUNDLE-PACKAGE(1)
Impressum