gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

added a ' quick search ' method. (#28660)

Browse Source
This commit is contained in:
75072107
2019-03-31 10:58:29 -07:00
committed by Christopher McCormack
parent 0c07ad1854
commit 7cbde1d724
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
guide/english/chef/index.md
View File

@ -8,11 +8,13 @@ title: Chef
Chef enables programmers and system administrators to work together. Instead of developers writing applications and then waiting on Ops staff to figure out how to deploy the software, Chef serves both communities. Chef moves the process from a herky-jerky release cycle to a continuous delivery model by enabling an effective and automated workflow—a central goal of the DevOps movement.
#### How Chef Works
<p>Chef stores collections of recipes in a cookbook. One cookbook should relate to a single task, but can have a number of different server configurations involved (for example a web application with a database will have two recipes, one for each part, stored together in a cookbook).</p>
Chef stores collections of recipes in a cookbook. One cookbook should relate to a single task, but can have a number of different server configurations involved (for example a web application with a database will have two recipes, one for each part, stored together in a cookbook).
<p>There is a Chef server which stores each of these cookbooks and as a new chef client node checks in with the server, recipes are sent to tell the node how to configure itself.</p>
There is a Chef server which stores each of these cookbooks and as a new chef client node checks in with the server, recipes are sent to tell the node how to configure itself.
<p>The client will then check in every now and again to make sure that no changes have occurred, and nothing needs to change. If it does, then the client deals with it. Patches and updates can be rolled out over your entire infrastructure by changing the recipe. There is no need to interact with each machine individually.</p>
The client will then check in every now and again to make sure that no changes have occurred, and nothing needs to change. If it does, then the client deals with it. Patches and updates can be rolled out over your entire infrastructure by changing the recipe. There is no need to interact with each machine individually.
Clients should be able to quickly find recipes they desire by using Tags. For example, a Beef Wellington may have tags such as 'beef', 'puff pastry', and 'steak'. This may help the client find not only the recipe he wants but other similar recipes that might pique his interest or suit his cooking style.
#### Chef Configuration
![Image Title](https://regmedia.co.uk/2015/10/07/chef_configuration_management.jpg "Chef Configuration process chart")