

Not with this setup, no. I specifically didn’t want The Algorithm™ involved.
openpgp4fpr:358e81f6a54dc11eaeb0af3faa742fdc5afe2a72
Not with this setup, no. I specifically didn’t want The Algorithm™ involved.
It’s much more lightweight, handles Plex integration much better and automatically cuts out ads, promotions, etc.
I moved from TubeArchivist to Pinchflat. Very good.
Containers are just processes with flags. Those flags isolate the process’s filesystem, memory [1], etc.
The advantages of containers is that the software dependencies can be unique per container and not conflict with others. There are no significant disadvantages.
Without containers, if software A has the same dependency as software B but need different versions of that dependency, you’ll have issues.
[1] These all depend on how the containers are configured. These are not hard isolation but better than just running on the bare OS.
It sounds like your port forwarding settings weren’t saved and the reboot has gone back to a previous configuration.
Untrue. I work for a global enterprise company that transacts hundreds of millions of dollars via LE certs.
SELinux
The reason is “asymmetric routing”. The return ping packets are traveling a different route on the way out than on the way back.
It would mean you’re entrusting the entire security of your network to Dockge’s authentication system.
… and for that reason, I’m out.
I use Rallly.
Ahhh… very good. I avoided all this by running Pihole on its own IP on the LAN using a bridged interface from the host.
This post from Stack Exchange might help you, switching 80 for 53, of course.
You don’t need UDP on port 80 forwarded through. HTTP is TCP only.
Nextcloud does all of this.
E2EE chat.
AudioBookshelf ticks all those requirements.
Enshittification at its finest.
Prometheus and Grafana. VictoriaMetrics as a drop-in replacement for long-term metric storage.