[chef] Re: Re: Re: [RFC] github.com/cookbooks

[Mark Van De Vyver < >]

Hi Alex,

Thanks for the feedback. I'll also try address your concerns/questions in the blog post.  

Two quick clarifications: 

 - We don't use Berkshelf but will happily entertain suggestions for www.cookbooks.io that make Berkshelf integration easier.  

 - github.com/cookbooks is the opposite of one big repository. Each cookbook has its own repo, and the account/organization tracks multiple vendors/indiviudals cookbooks.

Regards

Mark

On Wed, Nov 14, 2012 at 8:31 PM, Alex Howells < " target="_blank"> > wrote:

On 14 Nov 2012, at 04:13, " "> " < "> > wrote:

> Initial TODO is (essentially based on the roadmap stated in cookbooks/about):
> - extract tar.gz and zip archives of each repo's tags to www.cookbooks.io
> (delivered by the AWS ClouFront CDN)

Is this sustainable? I'm all for people and companies chipping in with
solutions, but as RubyGems knows this quickly becomes a $10000+ per
month bandwidth bill. Who's footing it and what happens when one day,
someone says "Wow that's a lot of money, how do we cut back in this
bit of the budget?" - what about all the users who're now relying on
it?

> - write a source for librarian-chef to retrieve archives from www.cookbooks.io

Don't forget Berkshelf!

> - regularize updating of github.com/cookbooks

As Noah said, I'm not sure what the logic behind one big repository is
now. Whilst I understand and accept folks have used this in the past,
is the effort worth it for the future?
>


Is there anything newer or better about the updates shipping here?
More cookbooks covered with test-kitchen or some other "nice to have"?