31–40 of 63 posts
load webserver.nlm (a reference for the old-timers here) Seems an odd feature for 1.9.11, why not wait for 2.0?
As long as it doesn't break API compatibility, why wait?
Earlier quoted context omitted.
Hugely important. Compiling your own Nginx has never been trivial in modern development pipelines, and until now that's been the only way to use external modules.
Honest question: Why do you think it was non-trivial? What is/was complex?
Earlier quoted context omitted.
Unfortunately, it looks like it may not be something will be able to work with. Instead of an ABI like Apache uses, Nginx went with signature checking. To load a precompiled module, the signature has to match. This means we would have to compile many different binary modules for every configuration people might have, and for every version of Nginx. Like several dozen. As it stands, though, the module system would be…
I would think that containers would help obviate such concerns, since it would be rather trivial to keep even a hundred images in place for an automated compilation run. Of course, serving the output would be harder, but still not impossible.
Earlier quoted context omitted.
Honest question: Why do you think it was non-trivial? What is/was complex?
I found that nginx actually "just works", however not all software is easy to compile and many of us shy away from compiling for various reasons.
Earlier quoted context omitted.
I found that nginx actually "just works", however not all software is easy to compile and many of us shy away from compiling for various reasons.
Compiling nginx is surprisingly easy and straightforward; a perfect example to get started with packaging for yourself.
Earlier quoted context omitted.
Hugely important. Compiling your own Nginx has never been trivial in modern development pipelines, and until now that's been the only way to use external modules.
Honest question: Why do you think it was non-trivial? What is/was complex?
I'd rather trust the package/security team of my favorite distribution to do this for me.
When you live in the modern world of cattle not pets you optimize for things like this.
That being said our current nginx solution lives in a Docker container on top of Kubernetes so it would be fairly trivial at this stage to build our own nginx and bake it in... but I have to pick my battles.
Earlier quoted context omitted.
I would think that containers would help obviate such concerns, since it would be rather trivial to keep even a hundred images in place for an automated compilation run. Of course, serving the output would be harder, but still not impossible.
How does containers help? Building a hundred different nginx's shouldn't be neither harder nor easier if you stuff the binary in a container or not.
For example, one Ubuntu machine with Docker can create build environments for every Linux based distro (and version thereof) that exists, and iterate through all of them when it comes time to build. The setup is not trivial, though it is easier than creating a similar environment with VMs or physical machines.
Earlier quoted context omitted.
Hugely important. Compiling your own Nginx has never been trivial in modern development pipelines, and until now that's been the only way to use external modules.
Honest question: Why do you think it was non-trivial? What is/was complex?
Although one advantage of requiring compilation is the user is probably more likely to use the latest version.
load webserver.nlm (a reference for the old-timers here) Seems an odd feature for 1.9.11, why not wait for 2.0?
Is this going to make it easier to enable stub_status module without compiling Nginx? (or buying NginxPlus) http://nginx.org/en/docs/http/ngx_http_stub_status_module.ht...
I'm using the nginx mainline PPA and didn't have a problem enabling it.