mahlon/symphony-metronome
1
0
Fork 0
Code Issues Pull requests Activity

Add 'last run' timestamps for recurring events, and take these into

Browse source 
account when firing events on daemon rescheduling (via HUP.)

FossilOrigin-Name: 1620e80e8bddd27741569dea0ff4bd84ba29429861ed49d17f5777c238ae4876
This commit is contained in:
mahlon@laika.com 2014-10-28 18:53:17 +00:00
parent b18647f6a5
commit 7c2954b0ad
6 changed files with 79 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

11
README.rdoc
View file

@ -50,7 +50,7 @@ Symphony connection information:
== Adding Actions
There are two primary components to Metronome -- getting actions into
There are two primary components to Metronome -- getting schedules into
its database, and performing some task with those actions when the time
is appropriate.
@ -76,6 +76,15 @@ starts up or receives a HUP signal, it will re-read and schedule out
upcoming work.
== Performing Work
Calling 'run' on the Metronome class is a blocking call, waking up upon
a scheduled event. The run method expects a ruby block, and it receives
the payload and the database ID of the scheduled event. Metronome is
unopinioned, what you do within this block is entirely up to you. See
the Synopsis section above for some examples.
== Options
Metronome uses