Difference between bundle and gem install? Ask Question. Asked 10 years, 5 months ago. Active 1 year, 9 months ago. Viewed 6k times. Improve this question. Rog Rog Add a comment. Active Oldest Votes. I'd say: by default on your local machine, no particular difference but This way in production, you have clearly separated apps with their own gems.
Even if the Rack team releases rack 1. This relieves a large maintenance burden from application developers because all machines always run the exact same third-party code. Of course, at some point, you might want to update the version of a particular dependency your application relies on. For instance, you might want to update rails to 4. Importantly, just because you're updating one dependency, it doesn't mean you want to re-resolve all of your dependencies and use the latest version of everything.
In our example, you only have three dependencies, but even in this case, updating everything can cause complications. To illustrate, the rails 4. Let's assume that the rails 4. However, we didn't specifically ask to update rack-cache , which may not be compatible with rack 1. And while an update from rack 1. In order to avoid this problem, when you update a gem, bundler will not update a dependency of that gem if another gem still depends on it.
In this example, since rack-cache still depends on rack , bundler will not update the rack gem. This ensures that updating rails doesn't inadvertently break rack-cache. Since rails 4. Since you originally declared a dependency on rails 4.
As described above, the bundle install command always does a conservative update, refusing to update gems or their dependencies that you have not explicitly changed in the Gemfile.
If rails 4. If you update your Gemfile , and your system already has all of the needed dependencies, bundler will transparently update the Gemfile. For instance, if you add mysql to your Gemfile and have already installed it in your system, you can boot your application without running bundle install , and bundler will persist the "last known good" configuration to the Gemfile. This can come in handy when adding or updating gems with minimal dependencies database drivers, wirble , ruby-debug.
In addition, the user deploying the application may not have permission to install gems to the system, or the web server may not have permission to read them. This may be overridden using the --path option. In some cases, that location may not be writable by your Unix 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. You should never use sudo bundle install. This is because several other steps in bundle install must be performed as the current user:. The third, however, can only be performed by actually invoking the git command as the current user.
As a result, you should run bundle install as the current user, and bundler will ask for your password if it is needed to put the gems into their final location. By default, bundle install will install all gems in all groups in your Gemfile 5 , except those declared for a different platform. However, you can explicitly tell bundler to skip installing certain groups with the --without option.
This option takes a space-separated list of groups. While the --without option will skip installing the gems in the specified groups, it will still download those gems and use them to resolve the dependencies of every gem in your Gemfile 5. 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. For a simple illustration, consider the following Gemfile 5 :. When you run bundle install --without production in development, we look at the dependencies of rack-perftools-profiler as well. That way, you do not spend all your time developing against Rack 2.
This should not cause any problems in practice, because we do not attempt to install the gems in the excluded groups, and only evaluate as part of the dependency resolution process. This also means that you cannot include different versions of the same gem in different groups, because doing so would result in different sets of dependencies used in development and production. Because of the vagaries of the dependency resolution process, this usually affects more than just the gems you list in your Gemfile 5 , and can surprisingly radically change the gems you are using.
For instance, if you run bundle install --without test , a subsequent call to bundle install that does not include a --without flag will remember your previous choice. In addition, a call to Bundler. At runtime, this remembered setting will also result in Bundler raising an exception if the Gemfile.
Subsequent calls to bundle install will install gems to the directory originally passed to --path. This may be overridden using the --path option. In some cases, that location may not be writable by your Unix 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.
You should never use sudo bundle install. This is because several other steps in bundle install must be performed as the current user:. The third, however, can only be performed by invoking the git command as the current user. As a result, you should run bundle install as the current user, and Bundler will ask for your password if it is needed to put the gems into their final location.
By default, bundle install will install all gems in all groups in your Gemfile 5 , except those declared for a different platform. However, you can explicitly tell Bundler to skip installing certain groups with the --without option. This option takes a space-separated list of groups. While the --without option will skip installing the gems in the specified groups, it will still download those gems and use them to resolve the dependencies of every gem in your Gemfile 5.
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.
For a simple illustration, consider the following Gemfile 5 :. When you run bundle install --without production in development, we look at the dependencies of rack-perftools-profiler as well.
That way, you do not spend all your time developing against Rack 2. This should not cause any problems in practice, because we do not attempt to install the gems in the excluded groups, and only evaluate as part of the dependency resolution process. This also means that you cannot include different versions of the same gem in different groups, because doing so would result in different sets of dependencies used in development and production.
Because of the vagaries of the dependency resolution process, this usually affects more than the gems you list in your Gemfile 5 , and can surprisingly radically change the gems you are using. When you run bundle install , Bundler will persist the full names and versions of all gems that you used including dependencies of the gems specified in the Gemfile 5 into a file called Gemfile.
Bundler uses this file in all subsequent calls to bundle install , which guarantees that you always use the same exact code, even as your application moves across machines. Because of the way dependency resolution works, even a seemingly small change for instance, an update to a point-release of a dependency of a gem in your Gemfile 5 can result in radically different gems being needed to satisfy all dependencies. If you do not, every machine that checks out your repository including your production server will resolve all dependencies again, which will result in different versions of third-party code being used if any of the gems in the Gemfile 5 or any of their dependencies have been updated.
When Bundler first shipped, the Gemfile. Over time, however, it became clear that this practice forces the pain of broken dependencies onto new contributors, while leaving existing contributors potentially unaware of the problem. Since bundle install is usually the first step towards a contribution, the pain of broken dependencies would discourage new contributors from contributing. As a result, we have revised our guidance for gem authors to now recommend checking in the lock for gems.
When you make a change to the Gemfile 5 and then run bundle install , Bundler will update only the gems that you modified. In other words, if a gem that you did not modify worked before you called bundle install , it will continue to use the exact same versions of all dependencies as it used before the update.
0コメント