Maybe we want /tmp/ of this machine on disk, because builds can get big, or we give it a lot of RAM, but I'm unsure if we want to reserve a lot of resources for a machine that does not do anything client facing.
I thing having a separate commit for this change might make bug hunting easier if this introduces a regression.
someone should read the README changes, but I don't have the peace of mind right now.
And there is nothing else that needs backup? Like for example a database for ticket sells?
So de we want more persistency things, or risking to never garbage collect on machines that restart often. The upside of this behavior would be that you never boot a new generation and run into a…
Hmm, i don't know how the nix store copy exactly works, my assumption was kind of that the target machine would optimize, when I copy to it. It will also substitute everything it can from cache,…
If someone knows a solution without mapAttrsToList let me know. It feels a bit like overkill. (esp. as we don't need the username here).
I changed the admin handling, please check extra careful. I don't want to brick all logins