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
14       install(1)][bundle-install], use the gems in the cache in preference to
15       the ones 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

SUPPORT FOR MULTIPLE PLATFORMS

24       When  using  gems that have different packages for different platforms,
25       Bundler 1.8 and newer support caching of gems for other platforms where
26       the  Gemfile  has  been resolved (i.e. present in the lockfile) in ven‐
27       dor/cache. This needs to be enabled  via  the  --all-platforms  option.
28       This setting will be remembered in your local bundler configuration.
29

REMOTE FETCHING

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