oschaaf commented on pull request #1939: URL: https://github.com/apache/incubator-pagespeed-mod/pull/1939#issuecomment-657280216
If all else fails, maybe the [CI config](https://github.com/apache/incubator-pagespeed-mod/blob/bazel/.travis.yml) can be helpful to figure out what's needed to bully the build into succeeding. warning: it can take quite a while. That's why the Envoy build is excluded over there: it takes more time then travis allows us. I think the plan you lay out would be viable, and NGINX could be taken out of the equation if it's only used as a vehicle to run pagespeed. But the Envoy port in here may need polish to make it comply with the routing you'd need, depending on how it needs to be configured, and it's still early stage / has no production mileage. High level, the rationale of the work here is project modernization, as well as creating (lots of) opportunities to lean up the project by piggy backing on Envoy/absl/bazel for a few things. Second, in a next step, the idea is to make the primary modus operandi running PageSpeed (v2) as a sideca for non-Envoy servers, either by documenting the required routing configuration or by providing a very thin module to set that up automatically. As Envoy is the vehicle of choice to facilitate running as a sidecar, no sidecar would be needed, as it will be able to run pagespeed directly with this extension compiled in. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
