Our great sponsors
-
infrastructure
The infrastructure monorepo for the Rocky Linux project. This project will be archived/deprecated in the future.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
> First, you won't use arch on production servers.
I don’t know, for a pet server this might not be as dumb an idea as it sounds (though without automatic updates, obviously). Perhaps with aconfmgr[1]?
I haven’t done it in anger, but over seven years of running a personal server I’ve had a total of three instances of breakage: upstream strongSwan systemd integration change[2] (in legacy config handling), upstream nftables parsing bug[3] (but I knew in advance that nftables is for adventurous people), and an upstream Kea config change[4] (and, well, Kea really bloody sucks—suggestions for anything else that can do DHCPv6 PD welcome). My (Arch) GNOME desktop broke much more frequently during that time.
[1] https://github.com/CyberShadow/aconfmgr
[2] https://wiki.strongswan.org/projects/strongswan/wiki/Changel..., first item
[3] https://git.netfilter.org/nftables/commit/?id=638af0ceb2b223...
[4] https://kb.isc.org/docs/en/upgrading-to-kea-16