Me

  • 24 Posts
  • 302 Comments
Joined 2 years ago
cake
Cake day: April 29th, 2023

help-circle

  • I have 4 6Tb HDDs which I got new from work: been running 24/7 for the last 6 years.

    The 4Tb drives they replaced where running for the previous 10 years (bought new as well) and are still in a drawer, got replaced only for the opportunity to upgrade to 6tb.

    If your refurbished last only 4 years, to be that is not a positive gain, you lost money. New drives should last 10 years in my personal (and debatable) experience. But I think those drives you bought will last more than 4 years.


  • Restic or Borg. For restic I use the great Backrest web GUI.

    I mounted an USB drive to one of my OpenWRT access points and backup on that one.

    Rclone or fuse can mount/access Google Drive and can be used as back end for your backup choice.

    Simplest backup ever: restic/Borg on a folder on the same PC. Not very recommendable, but indeed a good starting point.

    Zfs/brtfs seems a complex solution for a simple problem. True is that once you start eating you get hungrier so maybe worthwhile.









  • Not a bad take per-se, but a bit condescending. While I agree and like the KISS paradigm, remember that no solution works at a lower complexity level of the problem itself.

    So, define your problem clearly, find the simplest possible solution. Don’t overcomplicate, I agree, but don’t be fooled by false hopes.

    Is it really simpler? Yes. Will it scale if I need it to? Maybe not, but will I really need for it to scale?

    And so on.






  • Shimitar@feddit.ittoSelfhosted@lemmy.worldDNS?
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    2 months ago

    I have a quite rich selfhosted stack, and DNS is indeed part of it.

    For such a critical piece of infrastructure I didn’t needed a container, just installed Unbound and did some setup for ad blocking and internal DNS rules.

    Here my setup: https://wiki.gardiol.org/doku.php?id=router:dhcp-dns

    You could go with an independent pihole maybe, but that would double the chances of a hardware failure…

    Using one device for everything might seem risky, but actually has less chances of failure ;)




  • Well, here is the relevant part then, sorry if it was not clear:

    • Jellyfin will not play well with reverse proxy auth. While the web interface can be put behind it, the API endpoints will need to be excluded from the authentication (IIRC there are some examples on the web) but the web part will stil force you to double login and canot identify the proxy auth passed down to it.
    • Jellyfin do support OIDC providers such Authelia and it’s perfectly possible to link the two, in this case as i was pointing out, Jellyfin will still use it’s own authentication login window and user management, so the proxy does not need to be modified.

    TLDR: proxy auth doesnt work with Jellyfin, OIDC yes and it bypassess proxy, so in both cases proxy will not be involved.