30

I need to ensure some of my gems are installed from our own gem repository rather than rubygems, while the rest are installed from rubygems. Can I set this up in the Gemfile without worrying about a naming conflict with a identically named gem in Rubygems? How Can I determine where the gem is downloaded from?

eg Gemfile:

source :rubygems  
gem 'gemfromrubygems1'  
gem 'gemfromrubygems2'

source "http://our.own.gem.repo.com/the/path/to/it"  
gem 'gemfromourrepo'
Nakilon
  • 34,866
  • 14
  • 107
  • 142
mawk044
  • 493
  • 2
  • 5
  • 7

4 Answers4

47

Bundler 1.7 has a new feature that allows you to select the source for specific gems by nesting them in a block:

source "https://rubygems.org"

gem 'gemfromrubygems1' 
gem 'gemfromrubygems2'

source "http://our.own.gem.repo.com/the/path/to/it" do
  gem 'gemfromourrepo'
end

or specifying it as an option:

source "https://rubygems.org"

gem 'gemfromrubygems1' 
gem 'gemfromrubygems2'

gem 'gemfromourrepo', source: "http://our.own.gem.repo.com/the/path/to/it"

See http://bundler.io/v1.7/gemfile.html for details.

Tim Moore
  • 8,958
  • 2
  • 23
  • 34
6

According to the Source Priority section in the Gemfile manpage sources are searched from last entered to first entered.

Based on what you said, it sounds like you want to always prefer your gem over rubygems.org. As long as you don't need to vary your preference (ie. some dups from rubygems.org and some dups from your private repo) then your problem is solved simply with the following Gemfile:

source 'https://rubygems.org'
source 'http://our.own.gem.repo.com/the/path/to/it'

gem 'gemfromrubygems1'  
gem 'gemfromrubygems2'
gem 'gemfromourrepo'
Rory O'Kane
  • 29,210
  • 11
  • 96
  • 131
gtd
  • 16,956
  • 6
  • 49
  • 65
4

The only way I found seems like a horrible hack.

Bundler will search for the best version of your gem starting at the source listed last and then searching all the sources listed previously. It doesn't matter where the source lines are relative to the gem lines, only relative to each other.

I tried to make it work using :git and :path, but neither of those work for gemservers. That leaves matching the best version.

If you set the version of your gem to something like 2.mine.1 and push that to your server, you can constrain the version in your Gemfile.

source :rubygems
source 'http://myrepo'    
gem 'gemfromourrepo', '~> 2.ourrepo'

Then the best matching version should be one from your server. There's a chance someone could push their own gem of the same name with 2.ourrepo.2 to rubygems, but that is unlikely if it is unique.

Shawn Balestracci
  • 7,380
  • 1
  • 34
  • 52
  • I like this solution because it lets production pull from a production version of the gem, while in development I can pull from a development version of the gem. – LisaD Nov 30 '13 at 18:07
1

The path command might be able to help. It allows you to set gem specific sources

gem "foo", "1.0", :path => "bar"

Source:http://bundler.io/v1.3/man/gemfile.5.html

Btuman
  • 881
  • 2
  • 9
  • 37