You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
we just had the issue, that we were still using nginx 1.18.0 in our tests startNginx({ version: '1.10.0'}) but in the nginx.conf we were using js_var – a feature, that should not have worked with the njs version that was packaged with nginx 1.18.0. But the tests stayed green. Only when we deployed it, did it fail.
How can we avoid this in the future?
Thanks again for this great tool!
The text was updated successfully, but these errors were encountered:
Hi,
that’s because I always build nginx with the latest modules and dependencies at the time. njs is a separate module, it’s not shipped within the nginx tarball, so what do you mean by “njs version that was packaged with nginx 1.18.0”? This depends on particular distribution.
You can find the exact versions of modules and other dependencies the binary was built with in index.json (see IndexEntry). If you need some specific version, you can try to find it in history of the binaries branch.
OK – thanks for the explanation. I always just use the official nginx docker image (stable version) and don't do anything to the container after that.
So what I would find super helpful is a possibility to separately specify which njs version should be used in the tests. Would that even be possible?
Hi,
we just had the issue, that we were still using nginx 1.18.0 in our tests
startNginx({ version: '1.10.0'})
but in the nginx.conf we were usingjs_var
– a feature, that should not have worked with the njs version that was packaged with nginx 1.18.0. But the tests stayed green. Only when we deployed it, did it fail.How can we avoid this in the future?
Thanks again for this great tool!
The text was updated successfully, but these errors were encountered: