Skip to content
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

Single-fire option #35

Closed
robdejonge opened this issue Jan 3, 2022 · 2 comments
Closed

Single-fire option #35

robdejonge opened this issue Jan 3, 2022 · 2 comments
Assignees

Comments

@robdejonge
Copy link

Use case
Running the container as a script, just execute a single cycle

Describe the solution you'd like
While the container could be up and running and set with whatever poll frequency desired, for my use-case the polling is infrequent and upon request really. I'd like to be able to run the container with a single sync cycle instead of polling. Maybe if it's set to 0 or something?

Describe alternatives you've considered
I could start the container upon request, and have it automatically stopped after a set amount of time that ensures a sync completes but no second sync is started. While it would work, it's not exactly an elegant solution.

@robdejonge
Copy link
Author

Was reading the source code and noticed it actually breaks if the sync_interval in the configuration file is set to -1. Confirmed to work as expected. So, feature already exists!

@mandarons
Copy link
Owner

I love it when the issues gets closed without me doing anything. Thank you for taking some time to look into the code. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants