my trip learning this piece of configuration management 1. chef-solo becomes your best friend 2. You get more cocky with your cookbooks 3. Books-books-books you start reading all the books, blogs, tweets and what not, you get more and more confused disoriented 4. You think a Chef Server will answer all your problems, centralization is great right? 5. You refactor and write tests, realizing you’ve been doing it all wrong. A.K.A. GOTO 10 Taken from http://bit.ly/jj-chef-start
I started to write a “e-book” to fill in these gaps and walk someone through these steps • A pre-built chef_repo can be extremely intimidating, I never wish learning chef, and this new responsibility at the same time, on anyone • And unfortunately going into a company that uses chef there will probably already be a chef_repo there….
don’t get me wrong, but I’m writing this to help with the learning curve of chef after you’ve been trained • There is so much more in chef ecosystem than a 2 day bootcamp can you prepare for day-to- day administration; I’m writing this to help others because it’s so easy to get lost
a self paced FREE training that you can come out with the confidence to take over a chef_repo • I also want the book to be a “fail first” teaching method • How many times have I read something that was like “do this” and it assumes it works, but you miss something and you get a weird error and have no idea what happened • I want you to see the errors during the process
assuming I ever get that TARDIS or meet the Aschen on P4C-970 • Any Junior or Intermediate Admin that wants to learn chef because that’s what’s already there • A primer for a Linux Admin that wants to be as dangerous as possible as quickly as possible
next, what I’m missing. • Help writing or editing, my spelling and grammar is horrible • A good way to convert Markdown -> PDF there are a ton of options and I have no idea what I’m looking at • Eyes on this project • Thoughts on that “leanpub.com” type publishers? Is it even worth it?