I very highly recommend that you take the time and just switch. Caddy is simply fabulous. It’s designed to work (assuming it’s compiled with the module) with containers and use docker networks for routing. It makes it easy to spin up containers and directly reference the container names instead of remembering IP addresses and particularly comes in handy when your entire environment is containerized.

You can pull the caddy image and run it in docker and as long as your environment is configured correctly you can simply reverse_proxy @container and you’re done. Caddy pulls all the relevant port information directly from the container API.

I get such a nerd boner thinking about it.

You’re completely missing what he’s saying, and how that number is calculated. It’s an average connection speed over time and you’re anecdotally saying your internet is superior because you have a higher connection speed, which isn’t really true at all.

You have residential internet which is able to provide 3Gbps intermittently. You may even be able to sustain those speeds for several days at a time. But servers maintain those connections for months and years at a time…

800TB/mo is 2.469 Gb/s sustained for 30 days. They may be on a 10Gb/s connection, but that doesn’t mean they have enough demand to saturate it 100% of the time.