• 4 Posts
  • 440 Comments
Joined 2 years ago
cake
Cake day: April 27th, 2024

help-circle












  • Planning to host a Nix caching server, and have CI build all package and NixOS outputs on every push to git, then in turn pushing the output artifacts to the cache. Would save me a good chunk of time when tinkering with VMs that haven’t seen manual updates in a while.

    Only thing is, I’m not sure how to approach building and caching NixOS configs that receive agenix secrets in their input. Obviously those should not be cached…





  • More like: paying someone to maintain the hardware.

    Anyways.

    Just FYI, your mails with a provider like Proton are not E2E encrypted unless you exclusively wrote with other Proton customers (in which case I assume they are. No idea). Otherwise it’s just encrypted at rest.

    I dint really see the benefit over doing it completely yourself, not even offering metadata to a provider, and also having encryption at rest, while maintaining full compatibility with mail clients 🤔