Chef Automate was not previously open source but will be.
Always appreciate bugs being filed. I did a little pondering on the ticket the other day. Since we're using update-rc.d, we're likely talking about debian package install, which means that we could probably set the…
A large part of that was an unfortunate side-affect of gecode (a library Chef used for dependency resolution in Chef 10) not having a -nox package, thus pulling in libqt4-dev, which then spirals out of control. The…
Do it early, for many reasons. I worked as a systems administrator for startups before we wrote Chef, and I wouldn't go back to managing infrastructure by hand. A few reasons: * You don't have to maintain that database…
I'm sorry you feel that you didn't have a good experience. As one of the original Chef contributors before Opscode, and then becoming one of the lead people working with the open source community for Opscode, the…
It was a comical github issue related to @shanley basically accusing @csanz and @rekatz of @gklst of sexism. Someone has put a screenshot of the github issue here: http://imgur.com/a/cfblx#7 Geeklist has since issued an…
The importance of the Chef DSL is abstracting away common system interactions and most importantly, all the edge cases that come up. Whatever you are automating, you're going to be installing packages, starting…
If package management was as a happily solved of a problem as you imply, I think we would see fewer solutions out there. Each tends to solve for the needs of its own environment, users, and sometimes the whims and bias…
Opinions of Rubygems differ greatly and I would consider cargo culting gems as a distribution and dependency management infrastructure for Chef cookbooks to only be great for those who are strong with Ruby. Each…
Chef Automate was not previously open source but will be.
Always appreciate bugs being filed. I did a little pondering on the ticket the other day. Since we're using update-rc.d, we're likely talking about debian package install, which means that we could probably set the…
A large part of that was an unfortunate side-affect of gecode (a library Chef used for dependency resolution in Chef 10) not having a -nox package, thus pulling in libqt4-dev, which then spirals out of control. The…
Do it early, for many reasons. I worked as a systems administrator for startups before we wrote Chef, and I wouldn't go back to managing infrastructure by hand. A few reasons: * You don't have to maintain that database…
I'm sorry you feel that you didn't have a good experience. As one of the original Chef contributors before Opscode, and then becoming one of the lead people working with the open source community for Opscode, the…
It was a comical github issue related to @shanley basically accusing @csanz and @rekatz of @gklst of sexism. Someone has put a screenshot of the github issue here: http://imgur.com/a/cfblx#7 Geeklist has since issued an…
The importance of the Chef DSL is abstracting away common system interactions and most importantly, all the edge cases that come up. Whatever you are automating, you're going to be installing packages, starting…
If package management was as a happily solved of a problem as you imply, I think we would see fewer solutions out there. Each tends to solve for the needs of its own environment, users, and sometimes the whims and bias…
Opinions of Rubygems differ greatly and I would consider cargo culting gems as a distribution and dependency management infrastructure for Chef cookbooks to only be great for those who are strong with Ruby. Each…