Start with a simple, basic service. Think of something like a web server or ntp. Understand how these services affect your environment with respect to security, performance, availability, maintenance, backups, other services, firewalls, routing, DNS, monitoring and notification, documentation, change control, etc. Those are the hard parts of hosting and if you find ways to be effective with a simple service the others will be less daunting.
Exactly. The licensing and sublicensing structures in TV and film are way more complicated than in video games. They also intentionally license for relatively short durations for tax reasons and other corporate considerations that have nothing to do with the end viewer or consumer.
OMFG. Never knew there was something so awesome as Symfonium. Thanks! So easy to connect it to my Plex instance. GLEEEEEE.
If you don’t care about down time then feel free to consolidate all your apps to one postgresql instance. If you want to do maintenance on your DB it may impact all your other applications.
Thanks, this is a nice resource.
Sure, let’s add another layer of complexity for the user to set up their network, storage, and other external resources and call it easier and simpler.
My point isn’t that containers are bad. It’s just that there is often a push to containerise workloads that don’t require containers.
Containers are really only useful for scaling. I suppose there’s some benefit to isolation, but it’s not really that much better than just using correct permissions with SElinux.
OP is kinda right. Containers get overused unnecessarily.
A bit of topic; am I the only one that pronounces it “butterface”?