I use Rallly.
openpgp4fpr:358e81f6a54dc11eaeb0af3faa742fdc5afe2a72
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.
Yes, you can.
Without going into specifics, you need to share the network of your DB stack with the stack of the client containers.
Rather than NFS, perhaps iSCSI would be a better fit.
Use a single reverse proxy on that one port… it can then route the requests to the various back ends.
You probably want something that’s Docker-native like Traefik or Caddy.
This is true but if you’re self-hosting it’s not that much bother to add additional copies of a bridge for other users (granted, it’s not ideal).
It would mean you’re entrusting the entire security of your network to Dockge’s authentication system.
… and for that reason, I’m out.