- From: Three Tee <
>
- To: "
" <
>
- Subject: [chef] Re: Re: Re: Re: Re: Re: Orphaned Cookbooks?
- Date: Wed, 9 Jan 2013 09:46:31 -0800
+1 to this, especially as tools like berkshelf also encourage users to default to the community site for cookbooks. On Jan 9, 2013, at 4:58 AM, Cassiano Leal <
">
> wrote:
Looks good! I'll have a look at this one and maybe switch to using it.
Either way, I think that the community cookbooks should have a better management strategy in terms of cookbook usability.
It's quite daunting for a new user to go around hunting for better cookbooks on github than the ones in the opscode repo. This was a major source of anger and frustration for me when I was starting to learn Chef. :)
On Wednesday, January 9, 2013 at 10:52, Andrea Campi wrote:
On Wed, Jan 9, 2013 at 1:01 PM, Cassiano Leal <
" target="_blank">
> wrote:
I'll second the redis-angst as I'm going through it myself.
This [0] seems to be the most usable redis cookbook out there, but it hasn't been updated in a while and has to be patched in order to install the latest version of the redis server.
I'm currently using my own fork of it, but by looking through the pull requests it's obvious that there are other people in the same situation.
On Wednesday, January 9, 2013 at 09:58, Mike wrote:
Hey all,
There's been lackluster response to this.
I currently have this list:
* route53 * cassandra
* node, nodejs, npm - candidates for rollup * scout_agent
I know there's also some redis-angst out there.
-Mike
|
Archive powered by MHonArc 2.6.16.