Hi guys, I agree with you that today there are a lot of better web servers like traefik, caddy and so one, but nginx is still popular and so one people use it wrong... So I decided to open source my own variant of configs for it)
I would appreciate it, if you could annotate the config choices you made with the reason behind them. Example: sendfile on; # default is off tcp_nopush on; # default is off tcp_nodelay on; Why did you set those to on? What improvements do I get compared to the defaults?
Show HN: Nginx Common Useful Configuration
11–13 of 13 posts
Re: Show HN: Nginx Common Useful Configuration
#12glad to see this posted. nginx has driven me crazy the past 4 days. After reading and reading and reading, and experimenting.. I have a feeling that when I ran lets encrypt certbot, it added some things in files that were needed, but became a problem when I actually made the config files that were needed to point to the new folders.. I'm still not sure actually. I ended up just adding another domain name and configur…
We are what, 6 or 7 years after Let's Encrypt changed how we deal with certificates? The fact that nginx still requires the perfect incantation of certbot, cronjobs and whatnot is mind-boggling. I love nginx but it's hard to recommend it when other solutions exist that require zero fiddling and zero maintenance to get HTTPS working.
Re: Show HN: Nginx Common Useful Configuration
#13It suddenly feels like Nginx is a legacy system, in the same way Apache became a legacy system when Nginx was launched. If I need a web server my first instinct is to reach for Caddy, or if I just need a reverse-proxy then it's either Caddy or Traefik.