joaquin2020

4 ms·

1.
by joaquin2020 6y ago
> The alternative is ansible. Everybody I know moved away from Chef to Ansible and never looked back. That has been my experience/perspective as well. This was what I found industry... * ~2012 Puppet golden years * ~2014 Chef golde
2.
by joaquin2020 6y ago
I can give you SF Bay Area perspective, where Ruby and especially Rails is quite popular. With the arrival of Docker and Kubernetes, immutable infrastructure patterns dramatically reduce costs, and the need for a centralized change managem
3.
by joaquin2020 6y ago
Chocolatey is a proxy-package manager, automates fetching packages off the Internet installing them (often through the packages own .msi or other installer). So it doesn't compete against Chef any more than yum or apt-get or Homebrew
4.
by joaquin2020 6y ago
> I toyed with a simple puppet-alike, written in golang, called marionette (in hindsight a terrible name) Well, yeah, especially as Puppet has a well known solution named Marionette Collective * https://puppet.com/docs&#x
5.
by joaquin2020 6y ago
In the scope of config state management across mutable systems, SaltStack is the closest. When doing immutable infra, where managing desired state is only at deploy time, then Ansible is by far more popular. Beyond that you get into contain
6.
by joaquin2020 6y ago
Now I think I remember them. Weren't they an embedded database on Windows popular with PeachTree and such?
7.
by joaquin2020 6y ago
> Puppet is a great tool for managing containers, and so is Chef. There is nothing inherently good about YAML. I am not sure what complex config state management solution brings to the table for immutable containers. The state is immuta