diff options
Diffstat (limited to 'man')
-rw-r--r-- | man/bundle-cache.ronn (renamed from man/bundle-package.ronn) | 0 | ||||
-rw-r--r-- | man/bundle-install.ronn | 24 |
2 files changed, 12 insertions, 12 deletions
diff --git a/man/bundle-package.ronn b/man/bundle-cache.ronn index 78bbd88c4b..78bbd88c4b 100644 --- a/man/bundle-package.ronn +++ b/man/bundle-cache.ronn diff --git a/man/bundle-install.ronn b/man/bundle-install.ronn index d758dde3ea..e2df374e36 100644 --- a/man/bundle-install.ronn +++ b/man/bundle-install.ronn @@ -33,7 +33,7 @@ update process below under [CONSERVATIVE UPDATING][]. ## OPTIONS * `--force`: - Force download every gem, even if the required versions are already available + Force downloads every gem, even if the required versions are already available locally. * `--full-index`: @@ -63,7 +63,7 @@ update process below under [CONSERVATIVE UPDATING][]. will exit using a status code (`$?`). * `--retry=[<number>]`: - Retry failed network or git requests for <number> times. + Retries failed network or git requests for <number> times. * `--standalone[=<list>]`: Makes a bundle that can work without depending on Rubygems or Bundler at @@ -74,7 +74,7 @@ update process below under [CONSERVATIVE UPDATING][]. [remembered option][REMEMBERED OPTIONS]. * `--trust-policy=[<policy>]`: - Apply the Rubygems security policy <policy>, where policy is one of + Applies the Rubygems security policy <policy>, where policy is one of `HighSecurity`, `MediumSecurity`, `LowSecurity`, `AlmostNoSecurity`, or `NoSecurity`. For more details, please see the Rubygems signing documentation linked below in [SEE ALSO][]. @@ -83,7 +83,7 @@ update process below under [CONSERVATIVE UPDATING][]. By default, Bundler installs gems to the same location as `gem install`. -In some cases, that location may not be writable by a unprivileged user. In +In some cases, that location may not be writable by an unprivileged user. In that case, Bundler will stage everything in a temporary directory, then ask you for your `sudo` password in order to copy the gems into their system location. @@ -128,12 +128,12 @@ This is so that installing a different set of groups on another machine (such as a production server) will not change the gems and versions that you have already developed and tested against. -Bundler offers a rock-solid guarantee that the third-party -code you are running in development and testing is also the -third-party code you are running in production. You can choose -to exclude some of that code in different environments, but you -will never be caught flat-footed by different versions of -third-party code being used in different environments. +Bundler offers a guarantee that the third-party code you are +running in development and testing is also the third-party code +you are running in production. You can choose to exclude some of +that code in different environments, but you will never be caught +flat-footed by different versions of third-party code being used +in different environments. For a simple illustration, consider the following Gemfile(5): @@ -148,7 +148,7 @@ For a simple illustration, consider the following Gemfile(5): In this case, `sinatra` depends on any version of Rack (`>= 1.0`), while `rack-perftools-profiler` depends on Rack 1.x (`~> 1.0`). -When you configure bundler to exclude `production` with +When you configure Bundler to exclude `production` with `bundle config set without production` and run `bundle install` in development, we look at the dependencies of `rack-perftools-profiler` as well. That way, you do not spend all your time developing against @@ -258,7 +258,7 @@ does not work, run [bundle update(1)][bundle-update]. ## Transitioning from Bundler 1 Bundler 2 has removed several options from the CLI that are configurable -through the [bundle config(1))[bundle-config] command. +through the [bundle config(1)][bundle-config] command. The `path`, `with`, `without`, `frozen`, `deployment`, `shebang`, `clean` options can be set by using `bundle config`: |