-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish a "build" image to support custom module development #239
Comments
All the prerequisites are in Regarding the "build" image, it might make sense yes, if it includes:
PR are welcome! |
Would you need a "build image" per distribution? I assume building modules from source would require building on the same distribution as the intended runtime. What's the equivalent of |
You'd need the binaries to be compatible to the actual tag/nginx version you're building against, so indeed, you need to build on the same distribution. For apk, we've recently introduced nginx.org prebuilt packages, so you might want to re-use those to create new module packages. See http://hg.nginx.org/pkg-oss/file/tip/alpine for more details on that. |
Hi. I've added a way to make it easier to add modules on top of the official image, please check https://github.com/nginxinc/docker-nginx/tree/master/modules for more information. |
I'm just getting started with custom module development and I'm having a hard time getting the exact correct prerequisites and sources downloaded properly. Would it make sense to publish a "build" image Looks like it should be something like the first ~50 lines of this image, except without compiling and without cleaning up.
The text was updated successfully, but these errors were encountered: