On Monday, May 20, 2013 at 16:24, Morgan Blackthorne wrote:
Aha, yes, that's exactly what I was looking for. And I didn't even realize that site existed-- I've seen tickets.opscode.com, www.opscode.com/chef, cookbooks.opscode.com, and wiki.opscode.com... I never saw a link to docs.opscode.com before. Looking at it now, is it just me, or is there a lot of overlap between it and the wiki? I'm a little confused as to the point of each of the two of them, since they both offer documentation and in some cases, document the same exact thing.If d.o.c is more of an API-level documentation, then I could see that, but then I'd wonder if that could then be embedded into the wiki so that there's only one place to update and everything would always be in sync. OTOH, I know the Opscode folks have been revamping the site a lot lately (and I'm liking the new themes, btw!) so maybe this is part of the reorganization and duplication isn't something to be concerned about :)--~*~ StormeRider ~*~"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."(from Smallville Season 6x1: "Zod")
On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSSOn Mon, May 20, 2013 at 11:58 AM, Ranjib Dey < " target="_blank"> > wrote:oh.. sorryhome page of the doc categorized and enlists most of them, workflows tools, knife plugins, and many more.
http://docs.opscode.com/
e.g. chef community -> development toolsdoes this answer the question ?On Mon, May 20, 2013 at 11:53 AM, Mike < " target="_blank"> > wrote:I think Morgan is asking for people to list their toolset, not explain
the ones referenced.
More of: "I use these tools in this manner" kind of thing.
On Mon, May 20, 2013 at 2:30 PM, Ranjib Dey < " target="_blank"> > wrote:
> berkshelf - think of this as bundler or a package manager (like yum) [i know
> oversimplified]. It reads a file where you describe what cookbooks u need
> (with version) and from where to get them (chef servers, git repos, local
> files etc), it does the grabbing and assembling part of you , additionally
> it can also upload all of the cookbooks to a chef server.
> test-kitchen - an integration testing framework. You can write you tests,
> and then use test-kitchen to run them against multiple platform (aka
> operating system). Test kitchen also reads a file (.kitech.yaml) where you
> specify what to run in each platform etc.
>
> foodcritic - a lint tool. which check common styling errors against a
> predefined set of rules. this is not testing but more of style check (some
> of the checks strongly suggest there is a bug).
>
> i think chef-docs has a glossary .. if plase feel free to drop mails in the
> list, this will also serve as feedback for the docsite,
> ranjib
>
>
> On Mon, May 20, 2013 at 10:54 AM, Morgan Blackthorne < " target="_blank"> >
> wrote:
>>
>> I know that there's a keychain of an ecosystem built up around Chef. What
>> I don't really know is what the various parts are for. I see a bunch of them
>> mentioned on the list, on IRC, and occasionally git commits.
>>
>> Is there, or could there be, a page on the Chef wiki that talks about
>> tools related to Chef. Off the top of my head, it would include:
>>
>> Berkshelf
>> test-kitchen
>> food-critic
>> many more that I'm forgetting in my pain and Ambien haze...
>>
>> Having a short description of what it does and where to get it would be
>> awesome.
>>
>> --
>> ~*~ StormeRider ~*~
>>
>> "Every world needs its heroes [...] They inspire us to be better than we
>> are. And they protect from the darkness that's just around the corner."
>>
>> (from Smallville Season 6x1: "Zod")
>>
>> On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS
>
>
Archive powered by MHonArc 2.6.16.