Discussion
Sitting here after my morning coffee, contemplating using a proper configuration management system for my NetBSD hosts. Instead of the yanky shell scripts I wrote.
I'd still tangle those out from Org, but... perhaps they'd work better than my yank?
pkgin search "configuration management" shows me aegis, ansible, fossil, chef, puppet, and salt.
@cinebox I need more than putting files in the right place (that part was trivial to solve). I need stuff like installing packages, too.
By the looks of it, chef and puppet need ruby, and I'm not touching that with a ten feet pole, so that leaves me with ansible, aegis, and salt.
Salt has an agents/ directory, full with shit, ansible has AI infestation too, fossil is an SCM, not quite what I want, and so is aegis.
Fun.
Ok, lets browse through sysutils!
There's cfengine, again with the slop. plonk
There's rconfig, but that's not quite what I want either. mcollective's description has a lot of fancy words, and doesn't quite tell me much, and is in ruby. fabric is just a remote deployment tool, not configuration management. There's consul that's both Hashicorp and slop.
Then there's auto-admin, a whole lot of shell scripts, and no usable documentation.
..and that's about it. I guess I'm sticking with my yanky shell scripts.
@algernon I've been tempted to write my own configuration management system, in Rust. The configuration would be expressed in Rust, too, not in YAML or other stringly typed language.
@liw Aye, I've felt the temptation recently too. The only reason I'm able to resist is that in the long run, I don't want a configuration management system, but a declaratively configured system a'la NixOS or Guix.
Install bonfire.cafe
Get the full app experience
@algernon I'm using a git repo + stow. it's tolerable