You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Obviously this is only sorta useful with just one or two steps defined. I was hoping to meet up with more people at the Chef Summit Hack Day who are involved in teaching Chef to others (or are at various stages of learning about it themselves) and for a lesson plan to grow out of that conversation.
But it's okay, that conversation can take place here, too. Some of the more obvious "early" things:
Resources and recipes
Setting attributes and using them in a recipe. (Should also cover Ohai)
Adding a remote_file or cookbook_file to a recipe.
Adding a template.
Using attribute overrides to modify the output of a template.
Using notifications / subscriptions.
Basic multi-platform support with include_recipe and ohai / platform_family.
Managing Changes via Cookbooks
Cookbook versioning. (semver)
Sharing a cookbook with Supermarket.
Releasing a cookbook to a Chef organization.
The "environment/role cookbook" pattern.
Introducing the 'wrapper cookbook' pattern / introduction to Berkshelf.
Pinning to an older, known-good version of a cookbook with Berkshelf.
Berkshelf environments and applying/promoting them.
Extending Chef
Basic Ohai plugin?
Basic Chef start/rhandler?
Basic LWRP?
Basic HWRP?
The text was updated successfully, but these errors were encountered:
Obviously this is only sorta useful with just one or two steps defined. I was hoping to meet up with more people at the Chef Summit Hack Day who are involved in teaching Chef to others (or are at various stages of learning about it themselves) and for a lesson plan to grow out of that conversation.
But it's okay, that conversation can take place here, too. Some of the more obvious "early" things:
remote_file
orcookbook_file
to a recipe.The text was updated successfully, but these errors were encountered: