General discussion about Chef

[chef] Re: Re: Re: Re: Re: Re: Cooking Utensils...


Chronological Thread 
  • From: Mark Mzyk < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Re: Re: Cooking Utensils...
  • Date: Mon, 20 May 2013 16:07:13 -0400
Yes, docs.opscode.com is replacing the wiki. It is mostly being written by Opscode's tech writer, James Scott, who in my opinion is doing an awesome job (but I'm biased). It's all also on github, so you can send a PR if you see something that needs updating or adding: https://github.com/opscode/chef-docs

If you haven't seen Learn Chef, be sure to check that out as well https://learnchef.opscode.com/

Learn Chef contains tutorials as a compliment to the docs.

- Mark Mzyk, Opscode Dev

" type="cite">
" photoname="Ranjib Dey" src="jpgUpRNx71ew2.jpg" name="postbox-contact.jpg" height="25px" width="25px">
May 20, 2013 3:36 PM
the wiki is being migrated into docs (iirc)



" photoname="Morgan Blackthorne" src="jpg_cSi0XyGjA.jpg" name="postbox-contact.jpg" height="25px" width="25px">
May 20, 2013 3:24 PM
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/Ps3uSS



" photoname="Ranjib Dey" src="jpgUpRNx71ew2.jpg" name="postbox-contact.jpg" height="25px" width="25px">
May 20, 2013 2:58 PM
oh.. sorry
home 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 tools

does this answer the question ?


" photoname="Mike" src="jpgXnCVLNY2WX.jpg" name="postbox-contact.jpg" height="25px" width="25px">
May 20, 2013 2:53 PM
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.
" photoname="Ranjib Dey" src="jpgUpRNx71ew2.jpg" name="postbox-contact.jpg" height="25px" width="25px">
May 20, 2013 2:30 PM
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




Archive powered by MHonArc 2.6.16.

§