Lets recap what all we have done in the last blog :
1.) Setup workstation and chef-repo.
2.) Registered on chef to use hosted chef as the chef-server.
3.) Bootstrapped a node to be managed by the chef-server.
4.) Downloaded the “apache” cookbook in our chef-repo.
5.) Uploaded the “apache” cookbook to the chef-server.
6.) Added the recipe[apache] in the run-list of the node.
7.) Ran the chef-client on the client to apply the cookbook.
Now lets continue, and try to understand some more concepts around chef and see them in action.
Read More »
Below are the first steps in getting started with using chef.
The three main components of chef are :
1.) Work station
This is the developer’s machine will be used to author cookbooks and recipes and upload them to the chef-server using the command line utility called knife.
This is the main server on which all the cookbooks, roles, policies are uploaded.
This is the instance which would be provisioned by applying the cookbooks uploaded on the chef-server.
So, lets get started:
Read More »
Whenever we move to a new project, or we want to explore a new stack of technologies; we face the problem of environments. Being a developer we generally have a tendency to install everything on our local environment; which many times proves to be a disaster.
Today, modern web applications involve a lot of moving parts, numerous underlying technologies and a lot of complexity.Read More »
This is the ppt of my talk on devOps and Continuous Delivery using Chef which I had given in BeingAgile2013 Conference held at McKinsey