Start Self Hosting
The hardest part is drafting a series of questions for the end-user to understand and answer before we get that “MAGIC-PRESTO-CHANGO” get those configuration files that just works.<p>I blame the program providers.<p>Some Debian maintainers are trying to do this simple querying of complex configurations (dpkg-reconfigure &lt;`package-name&gt;`). And I applaud their limited inroad efforts there because no else one has seem to bother.<p>I have made a bash script to configure for each Chronyd, named, sshd, dhcpd, dhclient, NetworkManager, systemd-networkd, &#x2F;etc&#x2F;resolv.conf, amongst many. They try and ask simple questions and glue appropriate settings then run their own syntax checkers (most are provided by the original stream).<p>Postfix, Shorewall, and Exim4 remain a nightmare to my evolving design.
CISecurity and other government hardening docs were applied as well and then some I took even further like Chrony had its file permissions&#x2F;ownership even further and MitM block feature as well.<p>These are dangerous scripts where it can write files as root but as a user, you will instead get configuration files written out in appropriate directories under `build` subdirectory.<p>If these designs work across Redhat&#x2F;Fedora&#x2F;CentOS, Debian&#x2F;Devuan, and ArchLinux well, I may forge even further.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;egberts&#x2F;easy-admin" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;egberts&#x2F;easy-admin</a>