.\" generated with Ronn-NG/v0.9.1 .\" http://github.com/apjanke/ronn-ng/tree/0.9.1 .TH "CHAKE\-CHEF" "7" "December 2023" "" .SH "NAME" \fBchake\-chef\fR \- configure chake nodes with chef\-solo .SH "DESCRIPTION" This configuration manager will allow you to manage nodes by running \fBchef\-solo(1)\fR on each remote node\. .P When \fBchake init\fR runs, the following chef\-specific files will be created: .P A brief explanation of the created files that are specific to \fBchef\fR: .IP "\[ci]" 4 \fBconfig\.rb\fR: contains the chef\-solo configuration\. You can modify it, but usually you won't need to\. .IP "\[ci]" 4 \fBconfig/roles\fR: directory is where you can put your role definitions\. .IP "\[ci]" 4 \fBcookbooks\fR: directory where you will store your cookbooks\. A sample cookbook called "basics" is created, but feel free to remove it and add actual cookbooks\. .IP "" 0 .SH "CONFIGURATION" Nodes can be configured to be managed with chef by having a \fBrun_list\fR key in their configuration: .IP "" 4 .nf host1\.mycompany\.com: run_list: \- role[server] \- recipe[service1] service1: option1: "here we go" .fi .IP "" 0 .P Any extra configuration under \fBhost1\.mycompany\.com\fR will be saved to a JSON file and given to the chef\-solo \-\-node\-json option in the command line\. For example, the above configuration will produce a JSON file that looks like this: .IP "" 4 .nf { "run_list": [ "role[server]", "recipe[service1]" ] , "service1": { "option1": "here we go" } } .fi .IP "" 0 .P Inside Chef recipes, you can access those values by using the \fBnode\fR object\. For example: .IP "" 4 .nf template "/etc/service1\.conf\.d/option1\.conf" do variables option1: node["option1"] end .fi .IP "" 0 .SH "BOOTSTRAPPING" The bootstrap process for \fIchef\fR involves getting chef\-solo installed\. The node hostname will also be set based on the hostname informed in the configuration file\. .SH "SEE ALSO" .IP "\[ci]" 4 \fBchake(1)\fR .IP "\[ci]" 4 \fIhttps://docs\.chef\.io/\fR .IP "\[ci]" 4 \fIhttps://docs\.chef\.io/chef_solo\.html\fR .IP "" 0