Looking for: ngxpagespeed and naxsi tuts

[Ovidiu]

I've just switched to using nginx in conjunction with ISPCFG3 and am looking for tutorials to implement ngxpagespeed (the equivalent of mod_pagespeed for apache2; still in alpha) and naxsi (the equivalent of mod_security for apache2)

Both of them seem to need to necessitate a manual build (there is a nginx-naxsi package for Debian but it lacks several features of nginx-full)

[MaddinXx]

Originally Posted by Ovidiu

I've just switched to using nginx in conjunction with ISPCFG3 and am looking for tutorials to implement ngxpagespeed (the equivalent of mod_pagespeed for apache2; still in alpha) and naxsi (the equivalent of mod_security for apache2)

Both of them seem to need to necessitate a manual build (there is a nginx-naxsi package for Debian but it lacks several features of nginx-full)

So you need nginx-full features and it would not be helpful to have a manual on how to use it with nginx-naxsi package, right? Because using the nginx-naxsi package I could provide you with information, but not on how to compile a custom version (but it shouldn't be that hard - it's simply adding it during nginx build as an extra module).

Let me know

[Ovidiu]

Thanks for the feedback :-)

Well, my info relies on this: http://wiki.debian.org/Nginx
furtehr down the page you see a comparison of nginx-light, nginx-full and nginx-naxsi and I need some additional features to nginx-naxsi, i.e. the map and the cache purge feature.

If I found a good tutorial/how-to for compiling nginx by hand I'd be comfortable doing so.
My main concern about manually compiling is that I would have to compile nginx and forgetting to add some "module" I need.

I'm slightly confused about the nginx-extras package, it seems to contain everything. How is it meant to use? Can one install the nginx-extras and nginx-naxsi together and then have all those features available? If so, this would mean no extra compiling would be necessary.

[MaddinXx]

Well then, I guess it would be smartest to just compile a version including the modules you guess to need and see if everything works as expected - and if not, just compile a new version with additional features.

I've recently read a bit about nginx and dynamic module loading is neither implementer nor is it sure, if it will ever be implemented...so installing every nginx package @ debain is it's own nginx version.

[Ovidiu]

I don't really understand your statement here:

Originally Posted by MaddinXx

so installing every nginx package @ debain is it's own nginx version.

what do you mean by that? one has to decide i.e. if I try to install nginx-naxsi the other installed nginx versions are automatically removed:

apt-get install nginx-naxsi -u -s
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  nginx nginx-full
The following NEW packages will be installed:
  nginx-naxsi
0 upgraded, 1 newly installed, 2 to remove and 0 not upgraded.

btw. do you have a good tutorial/how-to/link on how to compile nginx by hand?

[MaddinXx]

yes, you can only have one version of nginx installed. To compare it with Apache, you can install single modules using apt/yum or whatever, because Apache allows you do load them dynamically (e.g. it can load .so modules from a given directory for example).

Because nginx does not allow that, every single nginx package will uninstall all others - because it does not only include some modules, but a whole nginx (since it does not allow dynamic module loading).

Hmmm, the one from pagespeed seems detailed enough: https://github.com/pagespeed/ngx_pagespeed

The ./configure, make and make install process is always the same - the important things are the parameters (like in the guide above, how they add modules).

Just be brave, you'll manage it