I really like Caddy, it used to do reverse proxying and file serving for my homelab, but more recently I've demoted it to just the file serving because of how awesome it is to be able to configure reverse proxying just using container labels, which is what Traefik allows me to do.
Check https://github.com/lucaslorentz/caddy-docker-proxy it's a Caddy plugin that does exactly this and in a less verbose way of Traefik.
Moreover if you have more of one caddy server deployed it handles TLS certification management in a shared environment, this thing it is not available in the Traefik open source edition (just with the enterprise solution).
It throws away decades of software engineering principles in favour of unchecked AI output by clicking “accept all” on the output.
You would certainly NOT use ‘vibe coded’ slopware that powers key control systems in critical infrastructure such as energy, banking, hospitals and communications systems.
The ones pushing “vibe coding” are the same ones who are all invested in the AI companies that power it (and will never disclose that).
An incident involving using ‘vibe coded’ slopware is just waiting to happen.