5 ms·
"The point is to make nginx's configuration dynamic and prevent bloating applications with stuff that belongs at the (lets call it) devops level." No, let's no
by sciurus 11y ago
"The point is to make nginx's configuration dynamic and prevent bloating applications with stuff that belongs at the (lets call it) devops level."
No, let's not call it that, because I have no idea what you mean when you say that.
- yc1010 11y agoSome nginx configuration files are very project specific, especially when you have projects using some of the modules they offer.
- CrLf 11y agoThrottling, request routing, security workarounds, integrating multiple applications under a single nginx reverse proxy, ... If you do ops or interact with an ops team, I'm sure you can find many more examples.
- sciurus 11y agoAgreed, those are all operational concerns and dynamic nginx configuration is great for that. I was objecting to seeing the term "devops" being further abused.