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

help-circle
  • Sorry, unfortunately can’t help you there. My matrix server is not federated, I remember back then I created an account on matrix.org specifically to read these. But maybe they got deleted in the meantime?

    Anyways, I have been really happy with continuwuity, to the point that up until now, I haven’t even looked at tuwunel again. The maintainers of continuwuity seem really nice and engaged, and both from a usage and stability point of view, as well as for the actually surprisingly fast release cycle, I have no complaints. I found and fixed a bug a couple weeks ago, and the dev process was also very friendly and relaxed.

    In short: while I don’t know how things are on the tuwunel side, I’m very happy to have gone with continuwuity and have high hopes for the future of the project.













  • 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 🤔



  • We host most stuff at home, and then additionally some services at Hetzner on an (auctioned) root server. Bloody nice to get really good hardware for cheap, plus unlimited data with either 1 or 10Gbit synchronous network speed, a dedicated IPv4,…

    Stuff like my mail server lives there because it HAS to be available, and doing it at home, and doing it well, is next to impossible.

    I’m planning a nix hydra + cache server, which will probably also live on the Hetzner server, simply because it’ll have pretty intense jobs to run a lot of the time and I’m not a fan of having the noise of spun-up fans at home.

    Both solutions have their place, is what I’m saying / agreeing.


    • every VM with state backs up its state to the NAS once a day
    • client devices rsync most of their home folder to the NAS once an hour
    • at 3:15 in the morning, a Borg backup job starts pushing the days changes to a Hetzner storage box

    Through borg, I have the Option to go back to any point in time with the backups. I will probably never need this, hence why it happens in this step, not on the rsync job to the NAS.

    Things like movies and tv shows are not backed up, they are replaceable. All in all, about 2tb of documents, pictures, and VM state is backed up to Hetzner, out of the 16tb on the NAS.

    Pick and choose your battles.