4 ms·
nginx config is only complicated if you want to take advantage of complex options. The config for a basic website is trivial. Seems like a poor tradeoff for a
by excitom 4y ago
nginx config is only complicated if you want to take advantage of complex options. The config for a basic website is trivial.
Seems like a poor tradeoff for a slower, less configurable web server.
- simon04 4y agoUnless you want a good HTTPS configuration. The output of https://ssl-config.mozilla.org/#server=nginx https://ssl-config.mozilla.org/#server=nginx is significantly longer than the one for caddy.
- francislavoie 4y agoFYI that website is outdated and unmaintained. The person who worked on it left Mozilla AFAIK (would love to be proven wrong). See https://twitter.com/CubicleApril/status/1438940565916225545 https://twitter.com/CubicleApril/status/1438940565916225545 The correct thing with Caddy is to _not configure anything at all_ for TLS. The defaults are the correct thing to use. If you override the defaults, then you're more at risk of bitrot due to not remembering to update your own config. Let Caddy (and the Go stdlib, really) choose what's secure.