You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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!
The text was updated successfully, but these errors were encountered:
Hi 👋
I had some fun yesterday debugging why my
rake
commands in theschedule.rb
somehow yielded different results than before without having changed anything towhenever
.It turns out, the
bundle_command
default is determined like so:whenever/lib/whenever/setup.rb
Line 26 in 0687268
..which is tied to:
whenever/lib/whenever.rb
Lines 31 to 33 in 0687268
Well. My seemingly unrelated change of the day was to move the
Gemfile
into a different location (say something likeGemfile-ruby33
) and point theBUNDLE_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 andbundle config gemfile
)I suggest to adjust
Whenever#bundler?
in a way that works in that scenario as well.Thanks!
The text was updated successfully, but these errors were encountered: