07:30 <jhass> whack: 1.10 will have that, gem install bundler --pre

08:27 <Daryn> Hi

08:28 <Daryn> I would like to know how to use the local repos feature, of bundler

08:28 <Daryn> I have two projects

08:28 <Daryn> one is dependent on the other

08:28 <Daryn> these are test projects

08:28 <Daryn> Jenkins runs the tests

08:29 <Daryn> We find that we have to constantly change the gem file

08:30 <Daryn> when jenkins runs, it points to the master branch of the remote repo

08:30 <Daryn> when we work on the tests, we want to use a local repo, or path

08:30 <Daryn> so we have to keep changing the gem file

08:31 <Daryn> is this expected with bundler?

08:33 <indirect> Daryn: you should use the git locals feature, explained at the bottom of this page: http://bundler.io/v1.9/git.html

08:52 <Daryn> Don't you still need to change the gem file when using git locals?

08:55 <Daryn> what if your local branch is not master

08:55 <Daryn> then you need to change the gem file to point to your branch, not so?

09:28 <arneb> Hey. I have a ruby appliaction in a docker container and I have the code mounted in. On deployment i run bundle install --deployment and then restart puma (the webserver). That works great on one docker machine. But when I start another one, bundle doesn't know I have a vendor folder and tells me it's missing gems.

09:28 <arneb> How can I tell bundle exec which folder to look for?

09:41 <arneb> I think I'll try rbenv-bundler, I will report back

10:09 <arneb> Okay, exporting BUNDLE_PATH like specified here: http://bundler.io/v1.3/man/bundle-config.1.html works, but it's missing a module

21:53 <dukedave> Is there a method buried somewhere deep in bundler, in to which I can pass a version and constraint (as strings), and be told whether the the version meets the constraint?

22:06 <dukedave> Answer: yes, but outside bundler: `Gem::Requirement.new('> 1.2').satisfied_by? Gem::Version.new('2.2')`