runitor start at ?

[r3mi]

Hello,
thanks again for runitor! It is my default solution when I need periodic (every) runs with Healthchecks.

Would you consider adding a parameter to have the first run at a specified time and/ or with a specified delay ? Then after, keep running with periodic timers.
Use case: I have a "human-facing" bot and need to schedule the periodic runs at convenient times (for the usual machine-related uses cases, I don't normally care for the time at which it runs).

May be (but I am not a Go developper), before the select loop with NewTicker and signal, adding a single select with NewTimer (and signal) ?

[bdd]

[...] first run at a specified time and/ or with a specified delay

The latter, specified delay, is simply sh -c "sleep N && runitor ...", right? I'm generally apprehensive of adding features that are trivially achievable via shell or other common Unix user space tooling. In fact -every is also achievable with a few lines of easy to comprehend shell, but it was an early addition, around the time I was limited to running periodic jobs ins very limited container runtimes.

Can you tell me more about your the human facing aspect you mention above? What does the scheduling look like? I interpreted it like, maybe, "run it at the top of every hour"; rather than: a date so in the future that runitor is blocked for hours, waiting for the specified run time. So, I wonder, if a subset of OnCalendar expression would be a better alternative.

e.g. runitor -on-time "0/6:00:00" cmd would run the command every 6 hours, at the top of the hour.

I'd like to set the expectations clearly here. I may not even start working on this for months. This is a single person project, and I'm pretty particular about not taking any dependencies.

[r3mi]

Hello, thanks for the reply!
I considered the sleep or some shell script, I agree it is a workable and simple solution.

For my use case: I have a bot that deliver old newspapers to some friends through messaging, and I would prefer to deliver at a a time of our choosing e.g. 7 AM or 7 PM.

I understand that you want to avoid unnecessary complexity of course. Again, thanks for your project!

[bdd]

I have the v1.5.0-beta.1 out, adding cron expression support with the -at flag.

For my use case: I have a bot that deliver old newspapers to some friends through messaging, and I would prefer to deliver at a a time of our choosing e.g. 7 AM or 7 PM.

For the above use case, you can run it like:

runitor -uuid <...> -at "00 07 * * *" -- command args...

Or you want to be fancy and do it both in the a.m and the p.m:

runitor -uuid <...> -at "00 07,19 * * *" -- command args...

Give it a whirl, let me know what you think.
https://github.com/bdd/runitor/releases/tag/v1.5.0-beta.1

[r3mi]

Nice.
I have done limited testing (I use the docker version normally) and it works great.
Thanks!