

In theory, yes.
Just keep in mind that the CPU is ARM-based and not all container images come with ARM variants.
openpgp4fpr:358e81f6a54dc11eaeb0af3faa742fdc5afe2a72


In theory, yes.
Just keep in mind that the CPU is ARM-based and not all container images come with ARM variants.


*you’re


Bullshit. That’s 10 characters per second.
This.
As someone that has their Pihole talking to DoH Mullvad upstream, what is described above is exactly how I did it.
… and punctuation, apparently.


Pinchflat is way less complicated than TubeArchivist and integrated with Plex without any extra work.


It does.
The IPv6 addresses isn’t pingable at all.
Neither the IPv4 or IPv6 addresses respond on port 443.


But even that will have some status code.
404? 500? 503?


You’ll probably need to provide more context. Is there an error message?
Is that someone’s chest hair in the background?


Haha. Oops. I should have checked first. Well done.


… or just publish the source on Github and let someone else continue the legacy.


Prometheus and Grafana. VictoriaMetrics as a drop-in replacement for long-term metric storage.


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.
You could always use Shamir’s Secret Sharing (SSS) and distribute your password recovery amongst trusted but unrelated friends.