`bundle_command` changes surprisingly when using a different Gemfile location
Author: makmicCreated Sep 6, 2024Updated Sep 6, 2024
Hi :wave:
I had some fun yesterday debugging why my rake commands in the schedule.rb somehow yielded different results than before without having changed anything to whenever.
It turns out, the bundle_command default is determined like so:
..which is tied to:
Well. My seemingly unrelated change of the day was to move the Gemfile into a different location (say something like Gemfile-ruby33) and point the BUNDLE_GEMFILE env variable to that location. That's not too common, but the standard way to do so (see https://bundler.io/v2.5/man/bundle-config.1.html#LIST-OF-AVAILABLE-KEYS and bundle config gemfile)
I suggest to adjust Whenever#bundler? in a way that works in that scenario as well.
Thanks!
Source: javan/whenever