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
However, the build instructions in the google/ngx_brotli repository warn us that we should use exactly the same configuration options that Nginx was built with, otherwise we will get an error:
"You will need to use exactly the same ./configure arguments as your Nginx configuration and append --with-compat --add-dynamic-module=/path/to/ngx_brotli to the end, otherwise you will get a "module is not binary compatible" error on startup. You can run nginx -V to get the configuration arguments for your Nginx installation."
Should the playbook be getting the configuration arguments with nginx -V, and then using them in the ./configure command?
The text was updated successfully, but these errors were encountered:
Thanks for the question. As far as I know, this warning does not take into account the fact that when you start installing the brotli module, it already uses exactly the same configuration as the installed nginx.
In any case, this playbook has been tested many times already on different VPS and never had a problem with it.
It seems the Brotli installation playbook builds the module like this:
However, the build instructions in the google/ngx_brotli repository warn us that we should use exactly the same configuration options that Nginx was built with, otherwise we will get an error:
Should the playbook be getting the configuration arguments with
nginx -V
, and then using them in the./configure
command?The text was updated successfully, but these errors were encountered: