diff options
| author | Hiroshi SHIBATA <hsbt@ruby-lang.org> | 2020-05-08 14:19:04 +0900 |
|---|---|---|
| committer | Hiroshi SHIBATA <hsbt@ruby-lang.org> | 2020-05-13 07:54:37 +0900 |
| commit | 0e60b59d5884edb8f9aea023efd9b24f1ff02049 (patch) | |
| tree | e52935ce510440872ca5ce6b0e092cbc94f18bc9 /man/bundle-cache.1.txt | |
| parent | 68224651a4d4dc3ce0cea666f5423dd8b6ba6cfc (diff) | |
| download | ruby-0e60b59d5884edb8f9aea023efd9b24f1ff02049.tar.gz | |
Update the bundler version with master branch
Diffstat (limited to 'man/bundle-cache.1.txt')
| -rw-r--r-- | man/bundle-cache.1.txt | 30 |
1 files changed, 15 insertions, 15 deletions
diff --git a/man/bundle-cache.1.txt b/man/bundle-cache.1.txt index c0b8b5bf07..31940ad999 100644 --- a/man/bundle-cache.1.txt +++ b/man/bundle-cache.1.txt @@ -1,4 +1,4 @@ -BUNDLE-CACHE(1) BUNDLE-CACHE(1) +BUNDLE-CACHE(1) BUNDLE-CACHE(1) @@ -9,19 +9,19 @@ SYNOPSIS bundle cache DESCRIPTION - Copy all of the .gem files needed to run the application into the ven- - dor/cache directory. In the future, when running [bundle + 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 The bundle cache command can also package :git and :path dependencies - besides .gem files. This needs to be explicitly enabled via the --all + 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 supports caching of gems for other platforms where the Gemfile + Bundler supports 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. @@ -36,9 +36,9 @@ REMOTE FETCHING - source "https://rubygems.org" + source "https://rubygems.org" - gem "nokogiri" + gem "nokogiri" @@ -50,22 +50,22 @@ REMOTE FETCHING 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 + 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. + 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 cache on an identical machine and check in - the gems. For instance, you can run bundle cache on an identical stag- - ing box during your staging process, and check in the vendor/cache + the gems. For instance, you can run bundle cache on an identical + staging box during your staging process, and check in the vendor/cache before deploying to production. By default, bundle cache(1) bundle-cache.1.html fetches and also @@ -75,4 +75,4 @@ REMOTE FETCHING - January 2020 BUNDLE-CACHE(1) + May 2020 BUNDLE-CACHE(1) |