• 0 Posts
  • 4 Comments
Joined 5 months ago
cake
Cake day: June 20th, 2024

help-circle
  • I remember the opposite - the discussions on Reddit had some quality threads with depth and actual knowledge. Someone would post a pic of some random ebay haul and they would receive 10 replies suggesting what they should have gotten instead, along with 18 bullet points explaining why.

    The threads here are either people asking how to set up some crappy *arr service on their first raspberry or why god created Jellyfin on the seventh day and not the first.

    I’ve been waiting since the exodus for the quality to increase here… Still hoping.



  • Keep it as simple as possible to start with and then expand if you feel there is a need. No need for two servers. The first thing you should buy though is a book about basic network design and security if you’re not familiar with it. It may feel like overkill now but future you will thank yourself.

    As for the family in the same house… I try to make it as seamless as possible. Sometimes there is no need to tell them because the new service I set up integrates nicely with our devices. And sometimes I tell them “we have X now which does this, you can go to http://x.y.z.lan or use the app”.

    Some random and probably not very popular opinions.

    • I would check out eBay for used parts and find a decent motherboard with an IPMI interface. Find an appropriate case with good reviews if you’re not gonna mount your server in a rack.

    • Install FreeBSD and use zfs in a raid configuration that fits you if you care about your data. Run all your services in separate jails and be done with it. You don’t need Docker anyway for your private NAS.

    • Plex, Jellyfin, the *arr stack and a few other resource hogging services have a nice web ui but that’s about it. Do you really, really, need transcoding and all the features? Set up NFS, DLNA or whatever and use whatever client you like. I can’t access my Jellyfin library right now because the backend is apparently too old (wtf). Meanwhile VLC and a few other more fancy frontend clients with cover art, ratings and stuff works just fine accessing the same files over NFS. You don’t have to run some convoluted bullshit and reinvent the wheel every time just because you can.

  • Any CalDAV server will do. All events are synced across all properly configured devices. No need for emailing individual events. Radicale is an exception. I also find it too simple/barebones.

    I have been running Baïkal for years. Multiple users and devices (iOS, Android, MacOS, Linux, Windows etc) with multiple calendars per user, a decent admin web ui, pretty lightweight, easy to install and configure and zero maintenance.

    Or just set up your own exchange server.

    Personally I miss a calendar frontend that can be used directly in a web browser. Like Google calendar but with everything living on my own server.

    Scheduling and event management should be done in a client if you ask me.