-
Notifications
You must be signed in to change notification settings - Fork 6
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
Periodic executor dispatch #34
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My main use-case for Pico is to run
docker-compose up -d
for config changes. However, if a container dies for some reason, bringing it back is done in two ways:One of the goals of the web UI (#10) is to provide a way to do this with a click instead of an ssh.
One of the goals of using an event bus (#27) is to allow multiple trigger sources for command execution.
It would make sense to introduce another provider (I guess we're calling event sources "providers" now?) that's based on periodic automated events (cron-tab style) alongside the Git events. So a target will react to Git pushes, but also run its command every now and then anyway.
At first, this felt like feature creep. I didn't really want to move towards a kubeapplier style reconcillation system because that would be very Docker-specific (but maybe...). I gave it some thought and realised this could be a useful solution that applies outside of Docker use-cases (periodically run a container, or a webhook, or any process, all configured via Git instead of via crontab where it gets buried in machine-specific config)
The text was updated successfully, but these errors were encountered: