03:27 <leif_> hi everyone, I have a question about vendoring, which is causing me an issue with guard-rspec and foreman - is this an appropriate place ?

03:37 <leif_> ok I'll just go ahead and start.

03:37 <leif_> When I do the following bundle install --path vendor/bundle --binstubs vendor/bundle/bin --jobs=4 everything installs as expected, and I see gem files where required etc. After that I do the following bundle exec foreman start which fires up guard and unicorn for me. Then I hit an issue. Guard is trying to setup guard-rspec, which in turn tries to run bundler. And I get this error. 13:31:49 guard.1 | /usr/local/var/rbenv/versio

03:37 <leif_> wow that did not format well, trying again

03:37 <leif_> When I do the following

03:38 <leif_> bundle install --path vendor/bundle --binstubs vendor/bundle/bin --jobs=4

03:38 <leif_> everything installs as expected, and I see gem files where required etc.

03:38 <leif_> After that I do the following

03:38 <leif_> bundle exec foreman start

03:38 <leif_> which fires up guard and unicorn for me. Then I hit an issue.

03:38 <leif_> Guard is trying to setup guard-rspec, which in turn tries to run bundler. And I get this error.

03:38 <leif_> 13:31:49 guard.1 | /usr/local/var/rbenv/versions/2.2.2/lib/ruby/site_ruby/2.2.0/rubygems/dependency.rb:315:in `to_specs': Could not find 'bundler' (>= 0) among 143 total gem(s) (Gem::LoadError)

03:39 <indirect> IRC only allows one line of text at a time

03:39 <leif_> And if I search my vendored gems, bundler is indeed not there.

03:39 <indirect> you’ll likely need to put the full error into a paste service

03:39 <leif_> I can do that - in a minute

03:39 <indirect> foreman doesn’t usually expect to be run by bundler

03:39 <leif_> A workaround this is to set my GEM_PATH as follows

03:39 <leif_> export GEM_PATH=/Users/leif/src/box_app/vendor/bundle/ruby/2.2.0:/usr/local/var/rbenv/versions/2.2.2/lib/ruby/gems/2.2.0

03:39 <leif_> This allows Guard to now find the installed bundler, and the error goes away and everything is sweet.

03:39 <indirect> I would expect that you need to change your Procfile to run `bundle exec guard` and `bundle exec unicorn`

03:39 <leif_> So my first thought is that bundler should vendor itself when we pass --path and --binstubs, and we just set the GEM_PATH to the vendored gems. Or that bundler, when it checks for vendored gems, sees that itself is vendored and makes sure guard-spec (and any other utility) will find itself there.

03:39 <leif_> Thoughts ?

03:40 <indirect> not a good idea

03:40 <leif_> foreman doesnt expect that ? is that documented as a best practice ?

03:40 <indirect> yes

03:40 <indirect> every example of how to use forman I have ever seen says to put `bundle exec` in your Procfile and to run `foreman start`, not `bundle exec foreman start`

03:41 <indirect> if you really want to install bundler into the bundled gems

03:41 <indirect> you can just run `bundle exec gem install bundler`

03:42 <indirect> by running `bundle exec foreman start`, you’re creating multiple nested bundler contexts

03:42 <leif_> ok - and the reason why vendoring bundler is a bad idea ?

03:42 <leif_> is it just in this scenario ?

03:42 <indirect> yeah

03:42 <indirect> just this scenario

03:42 <indirect> guard is written with the expectation that it will be run at a high enough level that it can load bundler

03:42 <indirect> as you saw with that exception

03:42 <indirect> guard could be written in such a way that it would work

03:43 <indirect> but they decided not to do that

03:43 <indirect> the fix is not to force bundler into the gems needed by your application (beacuse bundler is already installed at the system level)

03:43 <indirect> it’s to just run guard at the level that guard expects

03:43 <leif_> ok - the only thing that makes me uncomfortable is that foreman has a dependency on thor - as does guard - so its possbile/probably foreman will use one version of thor and guard (under foreman) another. Shoul I worry ?

03:43 <indirect> no

03:43 <indirect> they’re completely separate ruby processes

03:44 <indirect> foreman loads the system version of thor

03:44 <indirect> and then it creates a completely new ruby interpreter to run `bundle exec guard`

03:44 <leif_> ok I'll need to go away and think about that for a while.

03:44 <indirect> that ruby process loads bundler, which only allows the version of thor requested in the gemfile, and then guard loads that version of thor

03:46 <leif_> ok so thanx for helping. I appreciate it. I am concerned if I am setting my self up for a problem when I deploy to Heroku.

03:46 <leif_> but Heroku wont run foreman the way I am either I guess