Typo BUNDLER_GEMFILE -> BUNDLE_GEMFILE

[allaire]

I was wondering why puma was logging that I wasn't using puma via bundle exec when it was the case. Turns out ENV['BUNDLER_GEMFILE'] does not exists, ENV['BUNDLE_GEMFILE'] does:

ENV['BUNDLE_GEMFILE'] ||= File.expand_path('../../Gemfile', __FILE__)

[allaire]

Also @evanphx, should we activate prune_bundler by default when we detect the presence of a Gemfile and when the user has cluster mode, but without preload_app (since prune_bundler isn't compatible)? Is there any case where prune_bundler is not wanted when the user use both Bundler and Cluster mode without preload_app?

[evanphx]

That's a good question. I'm not yet sure because it does alter the behavior a little and I didn't want to surprise anyone with it. Perhaps for 3.0 we do it by default.

[allaire]

Yeah I vote for this too.

Last question about that: Is it sure that an error will happen if prune_bundler isn't set and we use phased restart with keep_releases 5 in Capistrano? I can't recall if this happened on our last project, but we often restarted the app without phased-restart!

[seuros]

Only if your gemfile changed.

[allaire]

@seuros makes sense, thx.