Closed devployment closed 9 years ago
Have to add that I'm using the current ChefDK. Maybe there's something wrong with their chef version or ruby version.
I'm running this cookbook with chef-solo without any problem. I use knife-solo as a tools. So I don't need to touch the solo.json
Ok. Maybe I'm doing it just wrong. But good to know that it works if done properly. :)
It's not part of this project or repository but would you mind to provide just a few points bullet list to get this initially running with chef/knife solo?
I'm going back learning the basics in the meantime.
@linc01n Are you using the ChefDK on the solo node? Or installed everything needed manually?
You don't need ChefDK at all unless you are developing cookbook.
I had a presentation slide on how to use knife-solo in 2013. You can take a look.
I think I figured out most of the things. Thanks for the help. :+1:
Not an issue in the cookbook I think. I'm currently trying to get familiar with Chef and thought this here might be a good exercise. Everything works as I try in with Vagrant in my local machine.
But if I try to run it on a "real" machine I'm struggling to overwrite the attribute values. Tried a
solo.json
file where I added the database configuration to use postgresql. This was passed in by -j. But the cookbook always tries to install mysql but gives me an error.So I tried to create data bags for the attributes. But same result.
Where does the attribute configuration go to make it run with chef solo?