-
Write a cookbook using you can install apache http server in CentOs and Ubuntu, enable the services and start the service.
-
Write a recipe using template resources to create a file, but only if an attribute has a specific value.
-
Write a recipe to create a file using a string, but not if “/etc/passwd” exists?
-
Write a cookbook to unzip a file, and then move a files from one location to another using batch, bash chef resources?
-
Create a role and assign any two cookbooks to role and setup a 2 nodes assigned to role and conerse the role.
-
Write a cookbook using install version of latest tomcat and deploy jenkins.war files into war.
-
Write a 4 cookbooks php, mysql, apache and webapp respectively and map a dependency between them and install a sample web application.
-
Write a cookbook to install git, wget, zip in RHEL and Ubuntu.
-
Write a cookbook in which create a file using a string, but only if “/etc/passwd” exists
-
Write a coobook to run a batch file that unzips and then moves files from one location to another.
Latest posts by scmgalaxy K (see all)
- Use of runtime variables to save into another variable using register in Ansible - September 6, 2018
- Ansible & Ansible Tower Variable Precedence Hierarchy - September 6, 2018
- How to use template in Ansible? - September 6, 2018
This blog is a great practical way to sharpen Chef skills because building multiple cookbooks makes you learn the “why” behind configuration management, not just the syntax. When you write cookbooks for common tasks (user management, package install, service setup, templating configs, cron jobs, log rotation, firewall rules, and app deployment), you naturally practice core Chef concepts like resources, recipes, attributes, templates, notifications, and—most importantly—idempotency (running the same code safely again and again). To get maximum value, treat each cookbook like a real project: keep it modular, use proper naming, add parameterized attributes, and include automated checks with Test Kitchen and InSpec so you can validate changes before production. Over time, these exercises build the mindset of writing predictable, maintainable automation that teams can trust.