• 0 Posts
  • 153 Comments
Joined 3 years ago
cake
Cake day: July 27th, 2023

help-circle
  • A great question. First of all, all of my services run with docker compose and use volumes for their config storage which get backed up regularly. Then I just use markdown files organized by having a separate file for each service. Basically anything I would need to reproduce my setup on a new machine is what I try to write down. All the docs and compose yaml files are versioned in git. I usually realize I left out info later on and add it as it occurs to me, typically if I have to set up the services on a new machine. This all applies to any software that needs more than a little config, not just apps hosted for the purpose of other machines using them. It’s a very imperfect process, but it’s a ton better than what I used to do which was think “eh I’ll remember how it’s setup”. I rarely would remember all the key details.













  • Every response I read here seems to get it. Yeah, you shouldn’t do risky things without understanding them first. By all means play around with self hosting without knowing anything at first, but do not expose your machine to the Internet without fully understanding the implications and do not complain that self hosting is hard. If you think it is, you just need a bit more education. It’s already incredibly easy these days.








  • Yes, they changed the free featureset, and afaik those changes were fair. Providing a tunnel for remote streaming for free doesn’t seem like a good business plan. I mean, yeah they could always back out of the promise of what a lifetime pass is, and if they do I will find a new solution and hope they’re sued for it.

    If they do back out of their lifetime commitment, I suspect that would drive some other similar apps to get better. Maybe I would even learn to live with jellyfin as it currently exists in that situation. But so far I don’t see a reason to, and that would almost have been true if I never paid for plex.