3 ms·
Nix/guix might be a better approach. Ansible and chef describe part of the desired state of a system and require a very large definition to cover the whole syst
by ptman 7y ago
Nix/guix might be a better approach. Ansible and chef describe part of the desired state of a system and require a very large definition to cover the whole system. nix aims to track the whole system state and allow you to supply changes which again combine to another whole system state
- pnutjam 7y agoFor tracking changes:http://sysconfcollect.sourceforge.net/ http://sysconfcollect.sourceforge.net/
- pas 7y agoYes. Though I'd probably want to simply use something "trusted", either Ubuntu LTS or CentOS/RHEL, keep the installed packages to a minimum, use a local repository mirror proxy, track package changes there, etc. And the image build should be just a simple imperative install these packages, use this config, run this command on invocation. Nix is rather amazing with its powerful CLI stuff it provides (S3 compatible dependency store, fetching via SSH, closures, etc). My only problem with NixOS is that it's very much like Gentoo. It has infinite composability built-in, but it means you have to rebuild everything. In Debian/Ubuntu land you usually can simply enable/disable install/uninstall specific feature related packages. (For example postfix and postfix-mysql packages.)