diff options
| -rw-r--r-- | man/bundle-package.1 | 55 | ||||
| -rw-r--r-- | man/bundle-package.1.txt | 79 | ||||
| -rw-r--r-- | man/bundle-package.ronn | 72 |
3 files changed, 0 insertions, 206 deletions
diff --git a/man/bundle-package.1 b/man/bundle-package.1 deleted file mode 100644 index 142f298cf4..0000000000 --- a/man/bundle-package.1 +++ /dev/null @@ -1,55 +0,0 @@ -.\" generated with Ronn/v0.7.3 -.\" http://github.com/rtomayko/ronn/tree/0.7.3 -. -.TH "BUNDLE\-PACKAGE" "1" "September 2019" "" "" -. -.SH "NAME" -\fBbundle\-package\fR \- Package your needed \fB\.gem\fR files into your application -. -.SH "SYNOPSIS" -\fBbundle package\fR -. -.SH "DESCRIPTION" -Copy all of the \fB\.gem\fR files needed to run the application into the \fBvendor/cache\fR directory\. In the future, when running [bundle install(1)][bundle\-install], use the gems in the cache in preference to the ones on \fBrubygems\.org\fR\. -. -.SH "GIT AND PATH GEMS" -Since Bundler 1\.2, the \fBbundle package\fR command can also package \fB:git\fR and \fB:path\fR dependencies besides \.gem files\. This needs to be explicitly enabled via the \fB\-\-all\fR option\. Once used, the \fB\-\-all\fR option will be remembered\. -. -.SH "SUPPORT FOR MULTIPLE PLATFORMS" -When using gems that have different packages for different platforms, Bundler 1\.8 and newer support caching of gems for other platforms where the Gemfile has been resolved (i\.e\. present in the lockfile) in \fBvendor/cache\fR\. This needs to be enabled via the \fB\-\-all\-platforms\fR option\. This setting will be remembered in your local bundler configuration\. -. -.SH "REMOTE FETCHING" -By default, if you run \fBbundle install(1)\fR](bundle\-install\.1\.html) after running bundle package(1) \fIbundle\-package\.1\.html\fR, bundler will still connect to \fBrubygems\.org\fR to check whether a platform\-specific gem exists for any of the gems in \fBvendor/cache\fR\. -. -.P -For instance, consider this Gemfile(5): -. -.IP "" 4 -. -.nf - -source "https://rubygems\.org" - -gem "nokogiri" -. -.fi -. -.IP "" 0 -. -.P -If you run \fBbundle package\fR under C Ruby, bundler will retrieve the version of \fBnokogiri\fR for the \fB"ruby"\fR platform\. If you deploy to JRuby and run \fBbundle install\fR, bundler is forced to check to see whether a \fB"java"\fR platformed \fBnokogiri\fR exists\. -. -.P -Even though the \fBnokogiri\fR gem for the Ruby platform is \fItechnically\fR acceptable on JRuby, it has a C extension that does not run on JRuby\. As a result, bundler will, by default, still connect to \fBrubygems\.org\fR to check whether it has a version of one of your gems more specific to your platform\. -. -.P -This problem is also not limited to the \fB"java"\fR platform\. A similar (common) problem can happen when developing on Windows and deploying to Linux, or even when developing on OSX and deploying to Linux\. -. -.P -If you know for sure that the gems packaged in \fBvendor/cache\fR are appropriate for the platform you are on, you can run \fBbundle install \-\-local\fR to skip checking for more appropriate gems, and use the ones in \fBvendor/cache\fR\. -. -.P -One way to be sure that you have the right platformed versions of all your gems is to run \fBbundle package\fR on an identical machine and check in the gems\. For instance, you can run \fBbundle package\fR on an identical staging box during your staging process, and check in the \fBvendor/cache\fR before deploying to production\. -. -.P -By default, bundle package(1) \fIbundle\-package\.1\.html\fR fetches and also installs the gems to the default location\. To package the dependencies to \fBvendor/cache\fR without installing them to the local install location, you can run \fBbundle package \-\-no\-install\fR\. diff --git a/man/bundle-package.1.txt b/man/bundle-package.1.txt deleted file mode 100644 index ff4068b3bd..0000000000 --- a/man/bundle-package.1.txt +++ /dev/null @@ -1,79 +0,0 @@ -BUNDLE-PACKAGE(1) BUNDLE-PACKAGE(1) - - - -NAME - bundle-package - Package your needed .gem files into your application - -SYNOPSIS - bundle package - -DESCRIPTION - Copy all of the .gem files needed to run the application into the ven- - dor/cache directory. In the future, when running [bundle - install(1)][bundle-install], use the gems in the cache in preference to - the ones on rubygems.org. - -GIT AND PATH GEMS - Since Bundler 1.2, the bundle package command can also package :git and - :path dependencies besides .gem files. This needs to be explicitly - enabled via the --all option. Once used, the --all option will be - remembered. - -SUPPORT FOR MULTIPLE PLATFORMS - When using gems that have different packages for different platforms, - Bundler 1.8 and newer support caching of gems for other platforms where - the Gemfile has been resolved (i.e. present in the lockfile) in ven- - dor/cache. This needs to be enabled via the --all-platforms option. - This setting will be remembered in your local bundler configuration. - -REMOTE FETCHING - By default, if you run bundle install(1)](bundle-install.1.html) after - running bundle package(1) bundle-package.1.html, bundler will still - connect to rubygems.org to check whether a platform-specific gem exists - for any of the gems in vendor/cache. - - For instance, consider this Gemfile(5): - - - - source "https://rubygems.org" - - gem "nokogiri" - - - - If you run bundle package under C Ruby, bundler will retrieve the ver- - sion of nokogiri for the "ruby" platform. If you deploy to JRuby and - run bundle install, bundler is forced to check to see whether a "java" - platformed nokogiri exists. - - Even though the nokogiri gem for the Ruby platform is technically - acceptable on JRuby, it has a C extension that does not run on JRuby. - As a result, bundler will, by default, still connect to rubygems.org to - check whether it has a version of one of your gems more specific to - your platform. - - This problem is also not limited to the "java" platform. A similar - (common) problem can happen when developing on Windows and deploying to - Linux, or even when developing on OSX and deploying to Linux. - - If you know for sure that the gems packaged in vendor/cache are appro- - priate for the platform you are on, you can run bundle install --local - to skip checking for more appropriate gems, and use the ones in ven- - dor/cache. - - One way to be sure that you have the right platformed versions of all - your gems is to run bundle package on an identical machine and check in - the gems. For instance, you can run bundle package on an identical - staging box during your staging process, and check in the vendor/cache - before deploying to production. - - By default, bundle package(1) bundle-package.1.html fetches and also - installs the gems to the default location. To package the dependencies - to vendor/cache without installing them to the local install location, - you can run bundle package --no-install. - - - - September 2019 BUNDLE-PACKAGE(1) diff --git a/man/bundle-package.ronn b/man/bundle-package.ronn deleted file mode 100644 index bc137374da..0000000000 --- a/man/bundle-package.ronn +++ /dev/null @@ -1,72 +0,0 @@ -bundle-package(1) -- Package your needed `.gem` files into your application -=========================================================================== - -## SYNOPSIS - -`bundle package` - -## DESCRIPTION - -Copy all of the `.gem` files needed to run the application into the -`vendor/cache` directory. In the future, when running [bundle install(1)][bundle-install], -use the gems in the cache in preference to the ones on `rubygems.org`. - -## GIT AND PATH GEMS - -Since Bundler 1.2, the `bundle package` command can also package `:git` and -`:path` dependencies besides .gem files. This needs to be explicitly enabled -via the `--all` option. Once used, the `--all` option will be remembered. - -## SUPPORT FOR MULTIPLE PLATFORMS - -When using gems that have different packages for different platforms, Bundler -1.8 and newer support caching of gems for other platforms where the Gemfile -has been resolved (i.e. present in the lockfile) in `vendor/cache`. This needs -to be enabled via the `--all-platforms` option. This setting will be remembered -in your local bundler configuration. - -## REMOTE FETCHING - -By default, if you run `bundle install(1)`](bundle-install.1.html) after running -[bundle package(1)](bundle-package.1.html), bundler will still connect to `rubygems.org` -to check whether a platform-specific gem exists for any of the gems -in `vendor/cache`. - -For instance, consider this Gemfile(5): - - source "https://rubygems.org" - - gem "nokogiri" - -If you run `bundle package` under C Ruby, bundler will retrieve -the version of `nokogiri` for the `"ruby"` platform. If you deploy -to JRuby and run `bundle install`, bundler is forced to check to -see whether a `"java"` platformed `nokogiri` exists. - -Even though the `nokogiri` gem for the Ruby platform is -_technically_ acceptable on JRuby, it has a C extension -that does not run on JRuby. As a result, bundler will, by default, -still connect to `rubygems.org` to check whether it has a version -of one of your gems more specific to your platform. - -This problem is also not limited to the `"java"` platform. -A similar (common) problem can happen when developing on Windows -and deploying to Linux, or even when developing on OSX and -deploying to Linux. - -If you know for sure that the gems packaged in `vendor/cache` -are appropriate for the platform you are on, you can run -`bundle install --local` to skip checking for more appropriate -gems, and use the ones in `vendor/cache`. - -One way to be sure that you have the right platformed versions -of all your gems is to run `bundle package` on an identical -machine and check in the gems. For instance, you can run -`bundle package` on an identical staging box during your -staging process, and check in the `vendor/cache` before -deploying to production. - -By default, [bundle package(1)](bundle-package.1.html) fetches and also -installs the gems to the default location. To package the -dependencies to `vendor/cache` without installing them to the -local install location, you can run `bundle package --no-install`. |