Keyoxide proof: $argon2id$v=19$m=64,t=512,p=2$/Bxo7QiXHH/MThwxZ1irnA$S8IDyQY5+tRZjnqvqnYcGQ

  • 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle




  • I guess it’s good to mention alternatives but imo Kyoo seems to be overkill for a homelab use case as its design goal appears to be to scale much better and serve a high user base and huge library. Just looking at the dependencies or compose.yml should make this apparent.
    Consequently the setup is much more complex and heavy to run compared to Jellyfin e.g.






  • Basically servers and Pis.

    If you wanted to host your own site and services, a Linux vps was (and still is) the only choice. Back then it was Debian, nowadays I use Arch on everything. Same with Raspberry Pis when the first one became available in 2012. With university I started using Arch on my laptop and later when Proton and Wayland became good, I moved to it on the Desktop as well.



  • I learned that using nix on arch for the home directory in addition to pacman and the aur is quite an unbeatable combo that I prefer to having everything managed by nix. The problem with nix and nixos I see for one is that it leaves some performance on the table for reproducibility and that many packages are or cannot be packaged for nix. Additionally arch already is quite reproducible albeit not as much as nixos. Writing your own meta package with a simple pkgbuild to manage the system base seemed like a good substitute for me.