On nginx, most of the upstream work on new features is in Nginx Plus, not benefitting free nginx. Several nginx devs have been disagreeing with the way this has been done and the way the project is being managed and left to work on forks. Maybe people who agree with the OP sentiment should look into freenginx and angie.
I wouldn’t say there’s anything bad about Nginx, but for a reverse proxy, Caddy just makes things so much easier since certificate issuance and management is the most frustrating thing about hosting web sites. At work, I pushed us to Caddy and we have 301 certificates running on it currently and it has zero issues with it. The other guys love how hands off it is too, especially now that I moved us to using Postgres for its storage.
Is there something bad about nginx that I’m missing?
I prefer it for reverse proxy over apache…I’d just always found it to be much simpler.
But going forward I’m more likely to use caddy or traefik.
P could very easily be python now. At least as a surrogate for Django.
On nginx, most of the upstream work on new features is in Nginx Plus, not benefitting free nginx. Several nginx devs have been disagreeing with the way this has been done and the way the project is being managed and left to work on forks. Maybe people who agree with the OP sentiment should look into freenginx and angie.
https://www.phoronix.com/news/Nginx-Forked-To-Freenginx
https://mailman.nginx.org/pipermail/nginx-devel/2024-February/K5IC6VYO2PB7N4HRP2FUQIBIBCGP4WAU.html
https://en.angie.software/angie/docs/
http://freenginx.org/
I wouldn’t say there’s anything bad about Nginx, but for a reverse proxy, Caddy just makes things so much easier since certificate issuance and management is the most frustrating thing about hosting web sites. At work, I pushed us to Caddy and we have 301 certificates running on it currently and it has zero issues with it. The other guys love how hands off it is too, especially now that I moved us to using Postgres for its storage.