Surely the SVGO package can be compiled into a browser bundle.

I might look into this myself…

Does this support SVG, i.e. SVGOMG/SVGO? If not, that’s a glaring omission.

I think it’s a good idea, everyone should be automating this anyway.

This is still not possible in all scenarios. For example, wildcard certificates for DNS providers with no API support.

I spent an unhealthy amount of time on Reddit. Getting bored of Lemmy is a feature, not a bug. Embrace it.

Terminals are powerful and flexible, but still slower than a dedicated UI to see states at a glance, issue routine commands, or do text editing.

Terminal absolutists are as insufferable as GUI purists. There is a place and time for both.

You should perhaps skim through https://docs.docker.com/storage/ quickly. That document explains that docker containers only have very limited persistence (this is kind of the whole point of containers). The only persistence of note is volumes. This is normally how settings are saved between recreating containers.

As for dependencies, well it’s possible that one container depends on the service of another. Perhaps this is what you are describing?

Either way, for more detailed help, you will have to explain your setup with more specific technical details.

No one else uses the term “cloud” like that.

That part of this comic really stuck out like a sore thumb. I can’t tell if it’s an oversight, a comment about the challenges of self-hosting, or subtle mockery of self-hosting hypocrisy.

This a 1/1000 likely outcome. Bankrupted companies will typically sell assets including IP and software to other companies to pay creditors (which excludes open sourcing them). And well before bankruptcy, any financial issues will cause Plex to be modified to support shitty monetization to the point that you won’t want the source code amyway.

Sorry for the bad outlook, better that you be ready than to hope for a unicorn.

I think the real benefits of Docker don’t become unquestionably obvious untill you’ve ever tried to manage more than one installation of some kind of server software in the same machine and inevitably learn the hard way that this comes with a lot of problems and downsides.

• From simple things like if the environment needs a restart, you can just restart the container, without rebooting the machine, interrupting other applications.
• To seriously dangerous and problematic things, like configuring your system to work with your new application only to realize that this configuration is breaking your other server software.