41 engineers on Hacker News describe using Chef first-hand: 6 endorse it, 7 regret it, 5 are mixed.
“I was a Puppet / Chef engineer for 8 years, never again.”
regret · production · 8 yr · ic0n0cl4st · 2021-03-11 · source ↗ · wrong label?“had used chef/puppet in bits and pieces before and was never that keen on them”
regret · personal · mijoharas · 2020-11-12 · source ↗ · wrong label?“every community cookbook I ever look at makes me less sure that that was the right call”
regret · production · xiaodown · 2017-05-09 · source ↗ · wrong label?“#1 has been the best in terms of ease of use and fire-and-forget.”
endorse · production · avitzurel · 2016-11-21 · source ↗ · wrong label?“With chef running the whole thing from scratch took that long by itself (after you installed all the software) and usually failed.”
regret · production · pbecotte · 2016-01-13 · source ↗ · wrong label?“Chef (same as runs in production) on top of Vagrant”
endorse · production · avitzurel · 2015-11-23 · source ↗ · wrong label?“We also built a tool around cluster/deploy management just like we had to do with chef.”
regret · production · siliconc0w · 2015-07-29 · source ↗ · wrong label?“At GitLab we use Chef Omnibus too and we love it.”
endorse · production · sytse · 2015-07-10 · source ↗ · wrong label?“we actually were using exact same artifact on machines set up with chef that were configured the same way as in prod”
endorse · production · takeda · 2015-06-30 · source ↗ · wrong label?“I've found tools like Chef don't work that well on windows but I might just be doing it wrong.”
regret · production · shubb · 2015-03-31 · source ↗ · wrong label?“We've been using chef in the past to manage docker, which never felt very good because the main cookbook was somewhat buggy (but it has gotten better recently).”
mixed · production · hobofan · 2014-11-19 · source ↗ · wrong label?“after using them both on earlier projects, we started looking for something else that could do orchestrations as well as provisioning and that had saner authentication”
regret · production · ermintrude · 2013-11-22 · source ↗ · wrong label?“It works pretty well so far; we'll almost certainly be looking at ways to make it easier”
endorse · production · Spoom · 2013-04-19 · source ↗ · wrong label?“I'm very active in the Chef / DevOps communities, and have been using/supporting OSS for over 10 years.”
endorse · production · jsul · 2012-11-13 · source ↗ · wrong label?“we use chef with the Opscode Platform and a git workflow for our chef repo, but that doesn't mesh as well with chef's versioning of cookbooks”
mixed · production · krobertson · 2011-10-19 · source ↗ · wrong label?“For cloud deployments chef works better for us... Yes, chef's claim to scalability is a joke.”
mixed · production · moe · 2011-10-09 · source ↗ · wrong label?“Once up and running most common every-day tasks are less painful in chef... The chef-implementation is an absolute and unmitigated disaster.”
mixed · production · moe · 2011-10-09 · source ↗ · wrong label?“It's worked well thus far but requires writing some bootstrap scripts for installing chef on a fresh instance”
mixed · production · 0.25 yr · pie · 2010-05-07 · source ↗ · wrong label?“I've also used Chef, custom RPM packages and classic Unix startup scripts.”
neutral · production · ekidd · 2023-12-18 · source ↗ · wrong label?“I've had similarly complicated problems with Terraform, Ansible, Chef and Puppet and just plain Linux as I have had with Kubernetes.”
neutral · personal · cameronh90 · 2021-09-07 · source ↗ · wrong label?“we migrated our Rails deployment from Chef to Ansible.”
neutral · production · pqdbr · 2020-11-17 · source ↗ · wrong label?“We used to use Chef years ago and replaced it with Ansible and Terraform and have zero regrets at 10^4 nodes.”
neutral · production · busterarm · 2020-10-23 · source ↗ · wrong label?“I just use the same chef, puppet or ansible playbook I will use for a physical server”
neutral · production · vikrantrathore · 2018-12-14 · source ↗ · wrong label?“In all my years of trying systems like Puppet, Chef, etc, I've never seen this work quite as well.”
neutral · personal · spectre256 · 2018-11-28 · source ↗ · wrong label?“We transitioned out of AWS where we had relatively well managed instances of our stack managed with chef and terraform”
neutral · production · halbritt · 2018-10-02 · source ↗ · wrong label?“we run Chef to manage our physical and virtual infrastructure.”
neutral · production · jdwithit · 2018-06-19 · source ↗ · wrong label?“we used to use Vagrant with Virtualbox and the Chef provisioner to create our dev environments”
neutral · production · jitl · 2017-09-07 · source ↗ · wrong label?“I ended up destroying/recreating so many droplets I just started using Chef.”
neutral · personal · krinchan · 2016-02-04 · source ↗ · wrong label?“I've never actually used Docker in production, I have some reasonable experience with Chef, a bit with Vagrant”
neutral · personal · dasil003 · 2015-06-19 · source ↗ · wrong label?“as a regular author of open-source chef cookbooks”
neutral · production · nathwill · 2015-05-09 · source ↗ · wrong label?“Right now we use Chef to provision the hosts and we run services normally.”
neutral · production · caw · 2014-11-19 · source ↗ · wrong label?“we just provision a new EC2 instance with Vagrant/Chef and it auto-joins the cluster.”
neutral · production · saryant · 2014-01-29 · source ↗ · wrong label?“At the moment we're just using Chef Solo because we only have four machines to deal with.”
neutral · production · saryant · 2013-12-01 · source ↗ · wrong label?“Erlang, haproxy, rabbitmq, redis, postgres, cassandra, chef”
neutral · production · metabrew · 2013-11-29 · source ↗ · wrong label?“We configure it using the same Chef code we use to build production”
neutral · production · igor47 · 2013-10-23 · source ↗ · wrong label?“app servers have chef scripts that stop/start the daemon and update the package.”
neutral · production · skyebook · 2013-10-21 · source ↗ · wrong label?“is the reason I know maven, ant, chef AND puppet, Jenkins, and gradle as well as I do.”
neutral · production · yajoe · 2013-09-04 · source ↗ · wrong label?“We switched from hand-configured boxes and a long, "full stack local" setup document to chef + vagrant at my current company”
neutral · production · pixelmonkey · 2013-06-09 · source ↗ · wrong label?“We have tools setup to do it for us (chef, in our case)”
neutral · production · Woost · 2011-09-30 · source ↗ · wrong label?“i've been using chef to automatically provision environments”
neutral · personal · gnubardt · 2010-10-08 · source ↗ · wrong label?