nginx customization best practices

[Jack Terranova]

We have a made some minor customizations to nginx to expose some of the
stub module metrics, so we can configure them through the access log.

We were able to follow the build-from-source instructions and made the
needed changes in the stub module.

We may make further changes, but were wondering what is the best practice
for maintaining a customized nginx repo?  Do we want to continue to
download release tar balls or should we fork the nginx GitHub repo and
build/release from the fork?

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20180425/729698ef/attachment.html>