Include ngx_pagespeed

[cloudfoundry]

Include ngx_pagespeed

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/126287561

The labels on this github issue will be updated when the story is started.

[CAFxX]

Starting with ngx_pagespeed 1.10.33 the module can also be built as a dynamic module, i.e. a module that needs to be explicitly loaded in nginx.conf. This means that buildpack users that don't need it have absolutely no additional attack surface or runtime impact.

[sesmith177]

We've created a story to further research including the ngx_pagespeed module

[sesmith177]

@CAFxX we are going to hold off on adding ngx_pagespeed for now. Specifically, we're waiting on the arrival of a more complete version of nginx's dynamic module functionality so that users can choose which modules to load

[CAFxX]

@sessmith can you elaborate a bit more? AFAICT what you're describing ("users can choose which modules to load") is exactly what dynamic modules are supposed to provide. Unless you mean you want to give users the ability to provide their own modules, but that's definitely out of scope for this ticket...

[RochesterinNYC]

@CAFxX what @sesmith177's comment means was that we're looking to potentially add and support Nginx's dynamic modules functionality in the future for this buildpack but it's currently relatively new and we'd like to adopt/support it when it's at a more stable, mature phase. Once dynamic modules are supported by this buildpack, ngx_pagespeed can be easily brought in by the app developer/buildpack user.