Seem the default repo on github didn’t take care of storing the node.json
in the repository.
e.g. https://github.com/opscode/chef-repo
What folder should I put my node.json?
(I think this file should also be maintained in the repo, right?)
Thanks.
On Wed, Feb 27, 2013 at 10:31 AM, howard chen howachen@gmail.com wrote:
Seem the default repo on github didn't take care of storing the node.json
in the repository.What folder should I put my node.json?
(I think this file should also be maintained in the repo, right?)
Yes, I think with chef-solo, the node.json is part of your repo.
It may contain the configuration of your cookbooks and the run_list.
However, there are different use-cases.
If you work with Vagrant, you might put part of your node.json directly
into your Vagrantfile too (that is part of your repo too).
If you invoke chef-solo from your host directly, see some interesting
discussion here:
Check out knife-solo [1], it makes working with chef solo a breeze and
stores the node json in './nodes/.json'
[1] GitHub - matschaffer/knife-solo: DEPRECATED: Please consider using https://knife-zero.github.io/, ansible, or visit https://www.chef.io/ for other ideas
Am 27.02.2013 10:48 schrieb "Patrick Mulder" mulder.patrick@gmail.com:
On Wed, Feb 27, 2013 at 10:31 AM, howard chen howachen@gmail.com wrote:
Seem the default repo on github didn't take care of storing the node.json
in the repository.What folder should I put my node.json?
(I think this file should also be maintained in the repo, right?)
Yes, I think with chef-solo, the node.json is part of your repo.
It may contain the configuration of your cookbooks and the run_list.
However, there are different use-cases.If you work with Vagrant, you might put part of your node.json directly
into your Vagrantfile too (that is part of your repo too).If you invoke chef-solo from your host directly, see some interesting
discussion here:
Idiomatic way to invoke chef-solo? - Server Fault