-
Notifications
You must be signed in to change notification settings - Fork 13
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
feature: Polling of repo for changes at a given interval #12
Comments
@djt , never mind ... I need to implement this. |
@djt , this is now part of |
Great, thanks so much Paul. Such great work you're doing with this. |
@greenpau I've been using this and it works great, one little bug though that may be due to my own config. I have the --watch flag run with caddy to update on config changes, and was recently testing out a new server config. It looks like the timer from the prior config does not end when a new one is loaded. A quick test will allow you to see, set "update every 1" in the config and then edit it to "update every 60", config will reload but the old timer will still run. If you repeat this, even for an unrelated config change, multiple timers can be seen running. Let me know if you need any further details, or if you'd rather me open a new issue. |
Polling to allow for private deployments to check repository for changes to trigger a pull.
Add Caddyfile directive:
I love the work you've done on this, I was quite disappointed when I found that references online to http.git were for caddy v1 so this really fills a void.
For servers that have open access it works great, but some internal work I do does not allow external traffic (for the webhook to hit) which is why the polling would be super beneficial.
The text was updated successfully, but these errors were encountered: