{ "content": [ { "type": "text", "text": "# bundle-install(1) (man)\n\n**Summary:** bundle-install - Install the dependencies specified in your Gemfile\n\n**Synopsis:** bundle install [--binstubs[=DIRECTORY]] [--clean] [--deployment] [--frozen] [--full-index]\n[--gemfile=GEMFILE] [--jobs=NUMBER] [--local] [--no-cache] [--no-prune] [--path PATH]\n[--quiet] [--redownload] [--retry=NUMBER] [--shebang] [--standalone[=GROUP[ GROUP...]]]\n[--system] [--trust-policy=POLICY] [--with=GROUP[ GROUP...]] [--without=GROUP[ GROUP...]]\n\n## Flags\n\n| Flag | Long | Arg | Description |\n|------|------|-----|-------------|\n| — | — | — | Binstubs are scripts that wrap around executables. Bundler creates a small Ruby file (a binstub) that loads Bundler, run |\n| — | --clean | — | On finishing the installation Bundler is going to remove any gems not present in the current Gemfile(5). Don´t worry, ge |\n| — | --deployment | — | In deployment mode, Bundler will ´roll-out´ the bundle for production or CI use. Please check carefully if you want to h |\n| — | --redownload | — | Force download every gem, even if the required versions are already available locally. |\n| — | --frozen | — | Do not allow the Gemfile.lock to be updated after this install. Exits non-zero if there are going to be changes to the G |\n| — | --full-index | — | Bundler will not call Rubygems´ API endpoint (default) but download and cache a (cur‐ rently big) index file of all gems |\n| — | --gemfile | | The location of the Gemfile(5) which Bundler should use. This defaults to a Gemfile(5) in the current working directory. |\n| — | --local | — | Do not attempt to connect to rubygems.org. Instead, Bundler will use the gems already present in Rubygems´ cache or in v |\n| — | --no-cache | — | Do not update the cache in vendor/cache with the newly bundled gems. This does not re‐ move any gems in the cache but ke |\n| — | --no-prune | — | Don´t remove stale gems from the cache when the installation finishes. This option is deprecated in favor of the noprune |\n| — | --path | | The location to install the specified gems to. This defaults to Rubygems´ setting. Bundler shares this location with Rub |\n| — | --quiet | — | Do not print progress information to the standard output. Instead, Bundler will exit using a status code ($?). |\n| — | --retry | [ | Retry failed network or git requests for number times. |\n| — | --shebang | | Uses the specified ruby executable (usually ruby) to execute the scripts created with --binstubs. In addition, if you us |\n| — | — | — | Makes a bundle that can work without depending on Rubygems or Bundler at runtime. A space separated list of groups to in |\n| — | --system | — | Installs the gems specified in the bundle to the system´s Rubygems location. This overrides any previous configuration o |\n| — | --trust-policy | [ | Apply the Rubygems security policy policy, where policy is one of HighSecurity, Medi‐‐ umSecurity, LowSecurity, AlmostNo |\n| — | --with | | A space-separated list of groups referencing gems to install. If an optional group is given it is installed. If a group |\n| — | --without | | A space-separated list of groups referencing gems to skip during installation. If a group is given that is in the rememb |\n\n## See Also\n\n- BUNDLE-INSTALL(1)\n\n## Section Outline\n\n- **NAME** (2 lines)\n- **SYNOPSIS** (5 lines)\n- **DESCRIPTION** (13 lines)\n- **OPTIONS** (6 lines) — 19 subsections\n - --binstubs[=] (11 lines)\n - --clean (5 lines)\n - --deployment (6 lines)\n - --redownload (2 lines)\n - --frozen (5 lines)\n - --full-index (4 lines)\n - --gemfile= (9 lines)\n - --local (4 lines)\n - --no-cache (4 lines)\n - --no-prune (4 lines)\n - --path= (7 lines)\n - --quiet (3 lines)\n - --retry=[] (2 lines)\n - --shebang= (6 lines)\n - --standalone[=] (6 lines)\n - --system (5 lines)\n - --trust-policy=[] (4 lines)\n - --with= (6 lines)\n - --without= (6 lines)\n- **DEPLOYMENT MODE** (34 lines)\n- **SUDO USAGE** (27 lines)\n- **INSTALLING GROUPS** (15 lines) — 4 subsections\n - ment and testing is also the third-party code you are runn (1 lines)\n - to exclude some of that code in different environments, (1 lines)\n - flat-footed by different versions of third-party code being (31 lines)\n - THE GEMFILE.LOCK (25 lines)\n- **CONSERVATIVE UPDATING** (42 lines) — 2 subsections\n - activesupport 2.3.8 (2 lines)\n - rack ~> 1.1.0 (19 lines)\n- **SEE ALSO** (10 lines)\n\n## Full Content\n\n### NAME\n\nbundle-install - Install the dependencies specified in your Gemfile\n\n### SYNOPSIS\n\nbundle install [--binstubs[=DIRECTORY]] [--clean] [--deployment] [--frozen] [--full-index]\n[--gemfile=GEMFILE] [--jobs=NUMBER] [--local] [--no-cache] [--no-prune] [--path PATH]\n[--quiet] [--redownload] [--retry=NUMBER] [--shebang] [--standalone[=GROUP[ GROUP...]]]\n[--system] [--trust-policy=POLICY] [--with=GROUP[ GROUP...]] [--without=GROUP[ GROUP...]]\n\n### DESCRIPTION\n\nInstall the gems specified in your Gemfile(5). If this is the first time you run bundle in‐\nstall (and a Gemfile.lock does not exist), Bundler will fetch all remote sources, resolve de‐\npendencies and install all needed gems.\n\nIf a Gemfile.lock does exist, and you have not updated your Gemfile(5), Bundler will fetch\nall remote sources, but use the dependencies specified in the Gemfile.lock instead of resolv‐\ning dependencies.\n\nIf a Gemfile.lock does exist, and you have updated your Gemfile(5), Bundler will use the de‐\npendencies in the Gemfile.lock for all gems that you did not update, but will re-resolve the\ndependencies of gems that you did update. You can find more information about this update\nprocess below under CONSERVATIVE UPDATING.\n\n### OPTIONS\n\nThe --clean, --deployment, --frozen, --no-prune, --path, --shebang, --system, --without and\n--with options are deprecated because they only make sense if they are applied to every sub‐\nsequent bundle install run automatically and that requires bundler to silently remember them.\nSince bundler will no longer remember CLI flags in future versions, bundle config (see bun‐\ndle-config(1)) should be used to apply them permanently.\n\n#### --binstubs[=]\n\nBinstubs are scripts that wrap around executables. Bundler creates a small Ruby file\n(a binstub) that loads Bundler, runs the command, and puts it in bin/. This lets you\nlink the binstub inside of an application to the exact gem version the application\nneeds.\n\nCreates a directory (defaults to ~/bin) and places any executables from the gem there.\nThese executables run in Bundler´s context. If used, you might add this directory to\nyour environment´s PATH variable. For instance, if the rails gem comes with a rails\nexecutable, this flag will create a bin/rails executable that ensures that all re‐\nferred dependencies will be resolved using the bundled gems.\n\n#### --clean\n\nOn finishing the installation Bundler is going to remove any gems not present in the\ncurrent Gemfile(5). Don´t worry, gems currently in use will not be removed.\n\nThis option is deprecated in favor of the clean setting.\n\n#### --deployment\n\nIn deployment mode, Bundler will ´roll-out´ the bundle for production or CI use.\nPlease check carefully if you want to have this option enabled in your development en‐\nvironment.\n\nThis option is deprecated in favor of the deployment setting.\n\n#### --redownload\n\nForce download every gem, even if the required versions are already available locally.\n\n#### --frozen\n\nDo not allow the Gemfile.lock to be updated after this install. Exits non-zero if\nthere are going to be changes to the Gemfile.lock.\n\nThis option is deprecated in favor of the frozen setting.\n\n#### --full-index\n\nBundler will not call Rubygems´ API endpoint (default) but download and cache a (cur‐\nrently big) index file of all gems. Performance can be improved for large bundles that\nseldom change by enabling this option.\n\n#### --gemfile=\n\nThe location of the Gemfile(5) which Bundler should use. This defaults to a Gemfile(5)\nin the current working directory. In general, Bundler will assume that the location of\nthe Gemfile(5) is also the project´s root and will try to find Gemfile.lock and ven‐‐\ndor/cache relative to this location.\n\n--jobs=[], -j[]\nThe maximum number of parallel download and install jobs. The default is the number of\navailable processors.\n\n#### --local\n\nDo not attempt to connect to rubygems.org. Instead, Bundler will use the gems already\npresent in Rubygems´ cache or in vendor/cache. Note that if an appropriate plat‐\nform-specific gem exists on rubygems.org it will not be found.\n\n#### --no-cache\n\nDo not update the cache in vendor/cache with the newly bundled gems. This does not re‐\nmove any gems in the cache but keeps the newly bundled gems from being cached during\nthe install.\n\n#### --no-prune\n\nDon´t remove stale gems from the cache when the installation finishes.\n\nThis option is deprecated in favor of the noprune setting.\n\n#### --path=\n\nThe location to install the specified gems to. This defaults to Rubygems´ setting.\nBundler shares this location with Rubygems, gem install ... will have gem installed\nthere, too. Therefore, gems installed without a --path ... setting will show up by\ncalling gem list. Accordingly, gems installed to other locations will not get listed.\n\nThis option is deprecated in favor of the path setting.\n\n#### --quiet\n\nDo not print progress information to the standard output. Instead, Bundler will exit\nusing a status code ($?).\n\n#### --retry=[]\n\nRetry failed network or git requests for number times.\n\n#### --shebang=\n\nUses the specified ruby executable (usually ruby) to execute the scripts created with\n--binstubs. In addition, if you use --binstubs together with --shebang jruby these ex‐\necutables will be changed to execute jruby instead.\n\nThis option is deprecated in favor of the shebang setting.\n\n#### --standalone[=]\n\nMakes a bundle that can work without depending on Rubygems or Bundler at runtime. A\nspace separated list of groups to install has to be specified. Bundler creates a di‐\nrectory named bundle and installs the bundle there. It also generates a bun‐‐\ndle/bundler/setup.rb file to replace Bundler´s own setup in the manner required. Using\nthis option implicitly sets path, which is a [remembered option][REMEMBERED OPTIONS].\n\n#### --system\n\nInstalls the gems specified in the bundle to the system´s Rubygems location. This\noverrides any previous configuration of --path.\n\nThis option is deprecated in favor of the system setting.\n\n#### --trust-policy=[]\n\nApply the Rubygems security policy policy, where policy is one of HighSecurity, Medi‐‐\numSecurity, LowSecurity, AlmostNoSecurity, or NoSecurity. For more details, please see\nthe Rubygems signing documentation linked below in SEE ALSO.\n\n#### --with=\n\nA space-separated list of groups referencing gems to install. If an optional group is\ngiven it is installed. If a group is given that is in the remembered list of groups\ngiven to --without, it is removed from that list.\n\nThis option is deprecated in favor of the with setting.\n\n#### --without=\n\nA space-separated list of groups referencing gems to skip during installation. If a\ngroup is given that is in the remembered list of groups given to --with, it is removed\nfrom that list.\n\nThis option is deprecated in favor of the without setting.\n\n### DEPLOYMENT MODE\n\nBundler´s defaults are optimized for development. To switch to defaults optimized for deploy‐\nment and for CI, use the --deployment flag. Do not activate deployment mode on development\nmachines, as it will cause an error when the Gemfile(5) is modified.\n\n1. A Gemfile.lock is required.\n\nTo ensure that the same versions of the gems you developed with and tested with are also\nused in deployments, a Gemfile.lock is required.\n\nThis is mainly to ensure that you remember to check your Gemfile.lock into version con‐\ntrol.\n\n2. The Gemfile.lock must be up to date\n\nIn development, you can modify your Gemfile(5) and re-run bundle install to conserva‐\ntively update your Gemfile.lock snapshot.\n\nIn deployment, your Gemfile.lock should be up-to-date with changes made in your Gem‐\nfile(5).\n\n3. Gems are installed to vendor/bundle not your default system location\n\nIn development, it´s convenient to share the gems used in your application with other ap‐\nplications and other scripts that run on the system.\n\nIn deployment, isolation is a more important default. In addition, the user deploying the\napplication may not have permission to install gems to the system, or the web server may\nnot have permission to read them.\n\nAs a result, bundle install --deployment installs gems to the vendor/bundle directory in\nthe application. This may be overridden using the --path option.\n\n### SUDO USAGE\n\nBy default, Bundler installs gems to the same location as gem install.\n\nIn some cases, that location may not be writable by your Unix user. In that case, Bundler\nwill stage everything in a temporary directory, then ask you for your sudo password in order\nto copy the gems into their system location.\n\nFrom your perspective, this is identical to installing the gems directly into the system.\n\nYou should never use sudo bundle install. This is because several other steps in bundle in‐‐\nstall must be performed as the current user:\n\n• Updating your Gemfile.lock\n\n• Updating your vendor/cache, if necessary\n\n• Checking out private git repositories using your user´s SSH keys\n\n\n\nOf these three, the first two could theoretically be performed by chowning the resulting\nfiles to $SUDOUSER. The third, however, can only be performed by invoking the git command as\nthe current user. Therefore, git gems are downloaded and installed into ~/.bundle rather than\n$GEMHOME or $BUNDLEPATH.\n\nAs a result, you should run bundle install as the current user, and Bundler will ask for your\npassword if it is needed to put the gems into their final location.\n\n### INSTALLING GROUPS\n\nBy default, bundle install will install all gems in all groups in your Gemfile(5), except\nthose declared for a different platform.\n\nHowever, you can explicitly tell Bundler to skip installing certain groups with the --without\noption. This option takes a space-separated list of groups.\n\nWhile the --without option will skip installing the gems in the specified groups, it will\nstill download those gems and use them to resolve the dependencies of every gem in your Gem‐\nfile(5).\n\nThis is so that installing a different set of groups on another machine (such as a production\nserver) will not change the gems and versions that you have already developed and tested\nagainst.\n\nBundler offers a rock-solid guarantee that the third-party code you are running in develop‐‐\n\n#### ment and testing is also the third-party code you are running in production. You can choose\n\n#### to exclude some of that code in different environments, but you will never be caught\n\n#### flat-footed by different versions of third-party code being used in different environments.\n\nFor a simple illustration, consider the following Gemfile(5):\n\n\n\nsource ´https://rubygems.org´\n\ngem ´sinatra´\n\ngroup :production do\ngem ´rack-perftools-profiler´\nend\n\n\n\nIn this case, sinatra depends on any version of Rack (>= 1.0), while rack-perftools-profiler\ndepends on 1.x (~> 1.0).\n\nWhen you run bundle install --without production in development, we look at the dependencies\nof rack-perftools-profiler as well. That way, you do not spend all your time developing\nagainst Rack 2.0, using new APIs unavailable in Rack 1.x, only to have Bundler switch to Rack\n1.2 when the production group is used.\n\nThis should not cause any problems in practice, because we do not attempt to install the gems\nin the excluded groups, and only evaluate as part of the dependency resolution process.\n\nThis also means that you cannot include different versions of the same gem in different\ngroups, because doing so would result in different sets of dependencies used in development\nand production. Because of the vagaries of the dependency resolution process, this usually\naffects more than the gems you list in your Gemfile(5), and can (surprisingly) radically\nchange the gems you are using.\n\n#### THE GEMFILE.LOCK\n\nWhen you run bundle install, Bundler will persist the full names and versions of all gems\nthat you used (including dependencies of the gems specified in the Gemfile(5)) into a file\ncalled Gemfile.lock.\n\nBundler uses this file in all subsequent calls to bundle install, which guarantees that you\nalways use the same exact code, even as your application moves across machines.\n\nBecause of the way dependency resolution works, even a seemingly small change (for instance,\nan update to a point-release of a dependency of a gem in your Gemfile(5)) can result in radi‐\ncally different gems being needed to satisfy all dependencies.\n\nAs a result, you SHOULD check your Gemfile.lock into version control, in both applications\nand gems. If you do not, every machine that checks out your repository (including your pro‐\nduction server) will resolve all dependencies again, which will result in different versions\nof third-party code being used if any of the gems in the Gemfile(5) or any of their dependen‐\ncies have been updated.\n\nWhen Bundler first shipped, the Gemfile.lock was included in the .gitignore file included\nwith generated gems. Over time, however, it became clear that this practice forces the pain\nof broken dependencies onto new contributors, while leaving existing contributors potentially\nunaware of the problem. Since bundle install is usually the first step towards a contribu‐\ntion, the pain of broken dependencies would discourage new contributors from contributing. As\na result, we have revised our guidance for gem authors to now recommend checking in the lock\nfor gems.\n\n### CONSERVATIVE UPDATING\n\nWhen you make a change to the Gemfile(5) and then run bundle install, Bundler will update\nonly the gems that you modified.\n\nIn other words, if a gem that you did not modify worked before you called bundle install, it\nwill continue to use the exact same versions of all dependencies as it used before the up‐\ndate.\n\nLet´s take a look at an example. Here´s your original Gemfile(5):\n\n\n\nsource ´https://rubygems.org´\n\ngem ´actionpack´, ´2.3.8´\ngem ´activemerchant´\n\n\n\nIn this case, both actionpack and activemerchant depend on activesupport. The actionpack gem\ndepends on activesupport 2.3.8 and rack ~> 1.1.0, while the activemerchant gem depends on ac‐‐\ntivesupport >= 2.3.2, braintree >= 2.0.0, and builder >= 2.0.0.\n\nWhen the dependencies are first resolved, Bundler will select activesupport 2.3.8, which sat‐\nisfies the requirements of both gems in your Gemfile(5).\n\nNext, you modify your Gemfile(5) to:\n\n\n\nsource ´https://rubygems.org´\n\ngem ´actionpack´, ´3.0.0.rc´\ngem ´activemerchant´\n\n\n\nThe actionpack 3.0.0.rc gem has a number of new dependencies, and updates the activesupport\ndependency to = 3.0.0.rc and the rack dependency to ~> 1.2.1.\n\nWhen you run bundle install, Bundler notices that you changed the actionpack gem, but not the\nactivemerchant gem. It evaluates the gems currently being used to satisfy its requirements:\n\n#### activesupport 2.3.8\n\nalso used to satisfy a dependency in activemerchant, which is not being updated\n\n#### rack ~> 1.1.0\n\nnot currently being used to satisfy another dependency\n\nBecause you did not explicitly ask to update activemerchant, you would not expect it to sud‐\ndenly stop working after updating actionpack. However, satisfying the new activesupport\n3.0.0.rc dependency of actionpack requires updating one of its dependencies.\n\nEven though activemerchant declares a very loose dependency that theoretically matches ac‐‐\ntivesupport 3.0.0.rc, Bundler treats gems in your Gemfile(5) that have not changed as an\natomic unit together with their dependencies. In this case, the activemerchant dependency is\ntreated as activemerchant 1.7.1 + activesupport 2.3.8, so bundle install will report that it\ncannot update actionpack.\n\nTo explicitly update actionpack, including its dependencies which other gems in the Gem‐\nfile(5) still depend on, run bundle update actionpack (see bundle update(1)).\n\nSummary: In general, after making a change to the Gemfile(5) , you should first try to run\nbundle install, which will guarantee that no other gem in the Gemfile(5) is impacted by the\nchange. If that does not work, run bundle update(1) bundle-update.1.html.\n\n### SEE ALSO\n\n• Gem install docs http://guides.rubygems.org/rubygems-basics/#installing-gems\n\n• Rubygems signing docs http://guides.rubygems.org/security/\n\n\n\n\n\n\nDecember 2021 BUNDLE-INSTALL(1)\n\n" } ], "structuredContent": { "command": "bundle-install", "section": "1", "mode": "man", "summary": "bundle-install - Install the dependencies specified in your Gemfile", "synopsis": "bundle install [--binstubs[=DIRECTORY]] [--clean] [--deployment] [--frozen] [--full-index]\n[--gemfile=GEMFILE] [--jobs=NUMBER] [--local] [--no-cache] [--no-prune] [--path PATH]\n[--quiet] [--redownload] [--retry=NUMBER] [--shebang] [--standalone[=GROUP[ GROUP...]]]\n[--system] [--trust-policy=POLICY] [--with=GROUP[ GROUP...]] [--without=GROUP[ GROUP...]]", "flags": [ { "flag": "", "long": null, "arg": null, "description": "Binstubs are scripts that wrap around executables. Bundler creates a small Ruby file (a binstub) that loads Bundler, runs the command, and puts it in bin/. This lets you link the binstub inside of an application to the exact gem version the application needs. Creates a directory (defaults to ~/bin) and places any executables from the gem there. These executables run in Bundler´s context. If used, you might add this directory to your environment´s PATH variable. For instance, if the rails gem comes with a rails executable, this flag will create a bin/rails executable that ensures that all re‐ ferred dependencies will be resolved using the bundled gems." }, { "flag": "", "long": "--clean", "arg": null, "description": "On finishing the installation Bundler is going to remove any gems not present in the current Gemfile(5). Don´t worry, gems currently in use will not be removed. This option is deprecated in favor of the clean setting." }, { "flag": "", "long": "--deployment", "arg": null, "description": "In deployment mode, Bundler will ´roll-out´ the bundle for production or CI use. Please check carefully if you want to have this option enabled in your development en‐ vironment. This option is deprecated in favor of the deployment setting." }, { "flag": "", "long": "--redownload", "arg": null, "description": "Force download every gem, even if the required versions are already available locally." }, { "flag": "", "long": "--frozen", "arg": null, "description": "Do not allow the Gemfile.lock to be updated after this install. Exits non-zero if there are going to be changes to the Gemfile.lock. This option is deprecated in favor of the frozen setting." }, { "flag": "", "long": "--full-index", "arg": null, "description": "Bundler will not call Rubygems´ API endpoint (default) but download and cache a (cur‐ rently big) index file of all gems. Performance can be improved for large bundles that seldom change by enabling this option." }, { "flag": "", "long": "--gemfile", "arg": "", "description": "The location of the Gemfile(5) which Bundler should use. This defaults to a Gemfile(5) in the current working directory. In general, Bundler will assume that the location of the Gemfile(5) is also the project´s root and will try to find Gemfile.lock and ven‐‐ dor/cache relative to this location. --jobs=[], -j[] The maximum number of parallel download and install jobs. The default is the number of available processors." }, { "flag": "", "long": "--local", "arg": null, "description": "Do not attempt to connect to rubygems.org. Instead, Bundler will use the gems already present in Rubygems´ cache or in vendor/cache. Note that if an appropriate plat‐ form-specific gem exists on rubygems.org it will not be found." }, { "flag": "", "long": "--no-cache", "arg": null, "description": "Do not update the cache in vendor/cache with the newly bundled gems. This does not re‐ move any gems in the cache but keeps the newly bundled gems from being cached during the install." }, { "flag": "", "long": "--no-prune", "arg": null, "description": "Don´t remove stale gems from the cache when the installation finishes. This option is deprecated in favor of the noprune setting." }, { "flag": "", "long": "--path", "arg": "", "description": "The location to install the specified gems to. This defaults to Rubygems´ setting. Bundler shares this location with Rubygems, gem install ... will have gem installed there, too. Therefore, gems installed without a --path ... setting will show up by calling gem list. Accordingly, gems installed to other locations will not get listed. This option is deprecated in favor of the path setting." }, { "flag": "", "long": "--quiet", "arg": null, "description": "Do not print progress information to the standard output. Instead, Bundler will exit using a status code ($?)." }, { "flag": "", "long": "--retry", "arg": "[", "description": "Retry failed network or git requests for number times." }, { "flag": "", "long": "--shebang", "arg": "", "description": "Uses the specified ruby executable (usually ruby) to execute the scripts created with --binstubs. In addition, if you use --binstubs together with --shebang jruby these ex‐ ecutables will be changed to execute jruby instead. This option is deprecated in favor of the shebang setting." }, { "flag": "", "long": null, "arg": null, "description": "Makes a bundle that can work without depending on Rubygems or Bundler at runtime. A space separated list of groups to install has to be specified. Bundler creates a di‐ rectory named bundle and installs the bundle there. It also generates a bun‐‐ dle/bundler/setup.rb file to replace Bundler´s own setup in the manner required. Using this option implicitly sets path, which is a [remembered option][REMEMBERED OPTIONS]." }, { "flag": "", "long": "--system", "arg": null, "description": "Installs the gems specified in the bundle to the system´s Rubygems location. This overrides any previous configuration of --path. This option is deprecated in favor of the system setting." }, { "flag": "", "long": "--trust-policy", "arg": "[", "description": "Apply the Rubygems security policy policy, where policy is one of HighSecurity, Medi‐‐ umSecurity, LowSecurity, AlmostNoSecurity, or NoSecurity. For more details, please see the Rubygems signing documentation linked below in SEE ALSO." }, { "flag": "", "long": "--with", "arg": "", "description": "A space-separated list of groups referencing gems to install. If an optional group is given it is installed. If a group is given that is in the remembered list of groups given to --without, it is removed from that list. This option is deprecated in favor of the with setting." }, { "flag": "", "long": "--without", "arg": "", "description": "A space-separated list of groups referencing gems to skip during installation. If a group is given that is in the remembered list of groups given to --with, it is removed from that list. This option is deprecated in favor of the without setting." } ], "examples": [], "see_also": [ { "name": "BUNDLE-INSTALL", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/BUNDLE-INSTALL/1/json" } ], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 5, "subsections": [] }, { "name": "DESCRIPTION", "lines": 13, "subsections": [] }, { "name": "OPTIONS", "lines": 6, "subsections": [ { "name": "--binstubs[=]", "lines": 11 }, { "name": "--clean", "lines": 5, "long": "--clean" }, { "name": "--deployment", "lines": 6, "long": "--deployment" }, { "name": "--redownload", "lines": 2, "long": "--redownload" }, { "name": "--frozen", "lines": 5, "long": "--frozen" }, { "name": "--full-index", "lines": 4, "long": "--full-index" }, { "name": "--gemfile=", "lines": 9, "long": "--gemfile", "arg": "" }, { "name": "--local", "lines": 4, "long": "--local" }, { "name": "--no-cache", "lines": 4, "long": "--no-cache" }, { "name": "--no-prune", "lines": 4, "long": "--no-prune" }, { "name": "--path=", "lines": 7, "long": "--path", "arg": "" }, { "name": "--quiet", "lines": 3, "long": "--quiet" }, { "name": "--retry=[]", "lines": 2, "long": "--retry", "arg": "[]" }, { "name": "--shebang=", "lines": 6, "long": "--shebang", "arg": "" }, { "name": "--standalone[=]", "lines": 6 }, { "name": "--system", "lines": 5, "long": "--system" }, { "name": "--trust-policy=[]", "lines": 4, "long": "--trust-policy", "arg": "[]" }, { "name": "--with=", "lines": 6, "long": "--with", "arg": "" }, { "name": "--without=", "lines": 6, "long": "--without", "arg": "" } ] }, { "name": "DEPLOYMENT MODE", "lines": 34, "subsections": [] }, { "name": "SUDO USAGE", "lines": 27, "subsections": [] }, { "name": "INSTALLING GROUPS", "lines": 15, "subsections": [ { "name": "ment and testing is also the third-party code you are running in production. You can choose", "lines": 1 }, { "name": "to exclude some of that code in different environments, but you will never be caught", "lines": 1 }, { "name": "flat-footed by different versions of third-party code being used in different environments.", "lines": 31 }, { "name": "THE GEMFILE.LOCK", "lines": 25 } ] }, { "name": "CONSERVATIVE UPDATING", "lines": 42, "subsections": [ { "name": "activesupport 2.3.8", "lines": 2 }, { "name": "rack ~> 1.1.0", "lines": 19 } ] }, { "name": "SEE ALSO", "lines": 10, "subsections": [] } ] } }