-
Notifications
You must be signed in to change notification settings - Fork 82
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
Avoid recompiling #10
Comments
It would of course make sense, and I would very much prefer it to be done like this It would have to be done with an only_when and quite a number of flags to be registered. I'm not really sure if it can be done easily. |
I am going to +1 this one, and mention when I do this to my vagrant machine--- it causes multiple instances of nginx to be running. Idea: could we just have a variable that we can set ourselves per-host? So, if we have "skip_nginx_compile: true" in a host_vars file--- it skips? A temporary stop-gap? |
+1 |
Perhaps you could write out the flags nginx was compiled to into a file and diff them in the task to see if it needs recompiling... I also had the issue with the old nginx still running, and I now use a handler for killing nginx processes on each re-provision.. |
Had a spare min so i put up a PR for this, let me know if fits the bill... |
Thank you @farridav |
Hi,
I wonder whether you'd like this role avoiding recompiling nginx?
When I use it several times in a row (for instance with
vagrant provision
, because I made some changes to my stack), it always recompile nginx although this is useless in this use case.The text was updated successfully, but these errors were encountered: