• 0 Posts
  • 22 Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle
  • Agree 100%. Most of the former Plex users turned Jellyfin users I have come across did so better Plex was broken in some way for them. For me it was the general lack of care in creating/maintaining a good Apple TV app. Over the past few years it’s just gotten buggier and buggier with a lot of complaints on the Plex forums where devs would essentially stop by to say they weren’t working on any fixes.

    Jellyfin doesn’t fix 100% of the issues, but at least there is active development on Swiftfin that showed a desire to fully support all devices.



  • I use Backblaze B2 through my Synology NAS to offsite my important data. Most things though I just backup locally and accept the risk of needing to rebuild certain things (like most of my movie/TV media files since I can just re-rip my physical media, and the storage costs are not worth the couple of days of time in that unlikely case).

    I really think this is key when thinking about your backup strategy that is specific to self hosting compared to enterprise operations. The costs come out of our pockets with no revenue to back it up. Managing backups for self hosting IMO is just as much about understanding your risk appetite and then choosing a strategy to match that. For example I keep just single copy in B2, since the failure mode I’m looking to protect against is catastrophic failure of my NAS which holds my main backups and media. I then use Proton Drive and OneDrive to backup secrets for my 2FA setups and encryption for my B2 bucket. This isn’t how I would do it at work (we have a fair more robust, but much more expensive setup). But my costs for B2 are around $15/mo which I am fine with. When I tried keeping multiple copies it had grown to over $50/mo before I cared enough to really rethink things (the cost of the hobby I told myself).







  • Asking broadly like this is akin to asking for a guide on how to cook, it’s generally too broad for there to be a single guide. You first need to figure out what your goals are (you state one already, you’d like it to be externally accessible), determine what services you want to host, and then start looking at how to do so.

    The advice I’d give is to start with a solid base, you’ll need something to self host on and it really shouldn’t be the PC you use for other things. Get it setup to run a virtualization OS such as proxmox and use that as your starting point. Then do a lot of reading. I spend probably three to four times as much time reading about the service I’m planning to deploy compared to actually doing the work to deploy it. Lastly, plan. You should have a solid plan in the beginning of how you want your service to work (what will be external vice internal only, how will you setup the networking stack to do that, are you going to have a domain, and will you use subdomains or folders to divide services, what does your IP space look like, will you host your own firewall to make the networking more controlled or fight with your ISPs router, do you want to use docker, kubernetes, or maybe full VMs for each service, do you want/need a UI to manage things from or are you comfortable with CLI, etc). These answers will lead you to guides for various services as well as service specific forums where help is more focused.







  • WxFisch@lemmy.worldtoSelfhosted@lemmy.worldplex or Jellyfin?
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    1
    ·
    2 years ago

    This is pretty much it, Plex offers far more client apps that are full featured and they make it super easy to setup and use both as an admin and a user. Especially for things like OTA TV where they provide the guide data once it’s setup (which is why it’s a paid option). I’d move to JellyFin in a heartbeat if they’d support OTA and DVR playback on AppleTV.


  • In most companies I’ve worked for, T1 is there to put in tickets from calls, and handle the simplest of tasks (password resets, account lockouts, “have you tried turning it off and on again” tasks). Anything beyond that is generally sent to T2 (usually the desktop team who then force other teams to accept tickets as needed) and T3 for anything that more systemic or needs deeper troubleshooting and system knowledge.

    In many places it’s a combination of piss poor pay creating little motivation and high turnover (and thus lack of training) and management prioritizing the wrong metrics (generally looking for short call times and short call queues). If you want to try and improve things I’d suggest learning about the KPIs that team is expected to meet, and then ask management why they chose those metrics. Generally I’ve found prioritizing first call resolution over call times to be a huge improvement to motivation of the team and user satisfaction scores (we all like solving problems and users tend to be way nicer when you fix the issue vice kick the can).

    I would say, at least to your point about them not having access to systems, that’s it’s very common for T1 to have pretty limited admin access to systems. Partly to protect against inexperience, but also as a social engineering protection. If they need to ask for access to pass a ticket for elevated rights, it gets another set of eyes on the call to ensure it’s all kosher.




  • Honestly I don’t really know. I don’t think it has to be but you’ll need to research what kind of certs you’ll need for your purposes and what options exists for a CA.

    My overall point was more that this isn’t really a “just setup Apache” web service, it’s a fair bit more involved since your looking for (I’m assuming) legally valid digital signatures which means they need to be secure, unique, identifiable, and adhere to non-repudiation. Services like DocuSign do all of that work already so unless you truly want open source because of passion or principles, this isn’t really a great area to try and roll your own without some experience and expertise.


  • Anything you use will need to generate secure certs for each user that signs which will need to be tied back to a root CA that is trusted by the clients device they are reading the signed documents on. Are you open to hosting all of the needed pieces to keep that working including buying the needed certs to chain trust?