Unforunately bundler likes to hijack all of the rubies everywhere. If you start foreman with a bundle exec foreman
it will make sure every single ruby program executed (even things like hub, gh, and vagrant) will all load up your bundle, and complain if they're not also inside the bundle.
The best solution is to use a system-installed foreman without bundle exec, and only bundle exec (or use binstubs for) the tools you want to load within the bundle environment.
A workaround is provided here which cleans the bundler env before starting the required subprocess.
This is a complicated issue but feel free to reach out to me: @sj26 or [email protected]
Something like:
$ git clone https://gist.github.com/8f638252ab64b1d0ecbb.git mailcatcher-test
Cloning into 'mailcatcher-test'...
...
$ cd mailcatcher-test
$ bundle
Installing/Using ...
...
Your bundle is complete!
$ bundle exec foreman start
14:45:16 web.1 | started with pid 54321
14:45:16 mailcatcher.1 | started with pid 54322
...
14:45:17 web.1 | [2014-05-07 14:45:17] INFO WEBrick::HTTPServer#start: pid=89203 port=9292
...
Go to http://localhost:9292