• 0 Posts
  • 20 Comments
Joined 2 months ago
cake
Cake day: February 2nd, 2026

help-circle




  • But as a result you’ll have a self-documented configuration-as-a-code that will allow you to scale your setup as you need. Reproducing something won’t require reading your notes, remembering your actions etc.

    Until you realise that

    • you don’t really need to scale a homelab that much
    • if something breaks, you just want to quickly fix it manually because “doing the Ansible” is more of a pain
    • now idempotency and documentation-as-code is out of the window. ;)

    (I’m being tongue-in-cheek here. I don’t doubt this may work for you, but it takes much more discipline than I have.)




  • Nice setup! I particularly like the kitchenowl deployment - it’s such an amazing tool and relatively unknown.

    One suggestion: the title header says “Family homepage”, yet the page contains admin tools that none other than you will ever use. I noticed that all this “admin clutter” was so off-putting that it kept others from actually using the dashboard. I’ve therefore created another homepage instance that showcases user-facing services only. It makes the UI much cleaner - and users more likely to actually find the services they may be looking for.


  • It’s not this or that. Security comes in layers. So while I would assume that the Jellyfin developers do their best to secure their application, I acknowledge the fact that bugs do exist and that Jellyfin is developed in and for hobbyist contexts, and thus not scrutinised and pentested for vulnerabilities in the way software meant for professional environments would be. Therefore I’ll add an extra layer of security by putting it behind a VPN that only whitelisted clients can access. If a vulnerability is detected, I can be sure it hasn’t already been exploited to compromise my server because we’re all “among friends” there.