bundler prune should be automatically detect #96
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
cc @evanphx |
seuros
added a commit
that referenced
this pull request
Mar 20, 2015
bundler prune should be automatically detect
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New behavier of puma_prune_bundler make my deployment crash again
In the case puma preload_app! is incompatible with puma_prune_bundler https://github.com/puma/puma/blob/master/examples/config.rb#L132
and puma will crash because of bundle context not switch between each capistrano deployment (even with the
puma:restart, which is using by default with preload_app)So here is my point
To make sure bundler is automatically switched between each deploy and do the right thing for preload_app or not.
@behe any idea?