# Rubygems source

**URL:** <https://discourse.chef.io/t/rubygems-source/4443>\
**Category:** Chef Infra (archive)\
**Created:** [September 11, 2013, 6:30pm UTC](https://discourse.chef.io/t/rubygems-source/4443 "2013-09-11T18:30:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Moser\_Kevin](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/moser_kevin/32/282_2.png) [@Moser\_Kevin](https://discourse.chef.io/u/Moser_Kevin)\
**Post date:** [September 11, 2013, 6:30pm UTC](https://discourse.chef.io/t/rubygems-source/4443/1 "2013-09-11T18:30:53Z")

</div>

All:

A little discussion point here. We run into an issue quite frequently with cookbooks from the community that assume access to [rubygems.org](http://rubygems.org), where we host an internal mirror and our servers don’t have access to [rubygems.org](http://rubygems.org).

We tend to create wrapper cookbooks and rewind a bunch of resources or add new recipes to the community cookbook just to let us specify new sources. Wanted to have some discussion around a more chef wide style override. Created a ticket for this and would be interested to have folks have some conversation on it and see what might be a good approach for everyone.

[https://tickets.opscode.com/browse/CHEF-4539](https://tickets.opscode.com/browse/CHEF-4539)

Thanks!!

Kevin

---

<div class="post-metadata">

**Author:** ![kallistec](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/kallistec/32/23_2.png) [@kallistec](https://discourse.chef.io/u/kallistec)\
**Post date:** [September 11, 2013, 6:37pm UTC](https://discourse.chef.io/t/rubygems-source/4443/2 "2013-09-11T18:37:26Z")

</div>

On Wednesday, September 11, 2013 at 11:30 AM, Moser, Kevin wrote:

> All:
> 
> A little discussion point here. We run into an issue quite frequently with cookbooks from the community that assume access to [rubygems.org](http://rubygems.org) ([http://rubygems.org](http://rubygems.org)), where we host an internal mirror and our servers don't have access to [rubygems.org](http://rubygems.org) ([http://rubygems.org](http://rubygems.org)).
> 
> We tend to create wrapper cookbooks and rewind a bunch of resources or add new recipes to the community cookbook just to let us specify new sources. Wanted to have some discussion around a more chef wide style override. Created a ticket for this and would be interested to have folks have some conversation on it and see what might be a good approach for everyone.
> 
> [https://tickets.opscode.com/browse/CHEF-4539](https://tickets.opscode.com/browse/CHEF-4539)
> 
> Thanks!!
> 
> Kevin  
> For the immediate term we've been handling stuff like this via Chef::Config options, so I think this could be okay for a future 11.x release. In the longer term (Chef 12ish, or maybe a "big" feature release of 11.x) we'd like to implement a means to configure global defaults for resource attributes.

--  
Daniel DeLeo

---

<div class="post-metadata">

**Author:** ![Moser\_Kevin](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/moser_kevin/32/282_2.png) [@Moser\_Kevin](https://discourse.chef.io/u/Moser_Kevin)\
**Post date:** [September 11, 2013, 6:40pm UTC](https://discourse.chef.io/t/rubygems-source/4443/3 "2013-09-11T18:40:35Z")

</div>

+1 for global defaults for resources!

From: Daniel DeLeo \<[dan@kallistec.com](mailto:dan@kallistec.com)[mailto:dan@kallistec.com](mailto:dan@kallistec.com)\>  
Reply-To: "chef@lists.opscode.com[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)" \<[chef@lists.opscode.com](mailto:chef@lists.opscode.com)[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)\>  
Date: Wednesday, September 11, 2013 11:37 AM  
To: "chef@lists.opscode.com[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)" \<[chef@lists.opscode.com](mailto:chef@lists.opscode.com)[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)\>  
Subject: [chef] Re: rubygems source

On Wednesday, September 11, 2013 at 11:30 AM, Moser, Kevin wrote:

All:

A little discussion point here. We run into an issue quite frequently with cookbooks from the community that assume access to [rubygems.org](http://rubygems.org)[http://rubygems.org](http://rubygems.org), where we host an internal mirror and our servers don’t have access to [rubygems.org](http://rubygems.org)[http://rubygems.org](http://rubygems.org).

We tend to create wrapper cookbooks and rewind a bunch of resources or add new recipes to the community cookbook just to let us specify new sources. Wanted to have some discussion around a more chef wide style override. Created a ticket for this and would be interested to have folks have some conversation on it and see what might be a good approach for everyone.

[https://tickets.opscode.com/browse/CHEF-4539](https://tickets.opscode.com/browse/CHEF-4539)

Thanks!!

Kevin  
For the immediate term we’ve been handling stuff like this via Chef::Config options, so I think this could be okay for a future 11.x release. In the longer term (Chef 12ish, or maybe a “big” feature release of 11.x) we’d like to implement a means to configure global defaults for resource attributes.

–  
Daniel DeLeo