Add support for individual feed poll timers #122
Conversation
Qinusty
force-pushed
the
qinusty/per-feed-polling
branch
2 times, most recently
from
3321806 to
f9d596e
Compare
feeds/README.md
Outdated
|
|
||
| `packages` this configuration option is only available on certain feeds, check the README of the feed you're interested in for information on this. | ||
|
|
||
| `schedule` this allows for polling to be configured on a schedule for this specific feed. This is supported by all feeds. The value for this field should match the format defined by the [cron library](https://pkg.go.dev/github.com/robfig/cron#hdr-CRON_Expression_Format), intervals and predefined schedules are also supported. |
There was a problem hiding this comment.
Having the main option of poll_rate parsed as time.Duration and feed specific schedules as cron formatted strings might be slightly confusing for users. Do we want to be consistent here? poll_rate has the caveat that it's used as an actual duration value too for the cutoff.
There was a problem hiding this comment.
Hmmm... perhaps it's worth restricting this value to be intervals set as time.Duration parsable strings which we can prepend with @every.
I think this is flexible enough for most usecases.
There was a problem hiding this comment.
I'd vote for the prepending where necessary :)
There was a problem hiding this comment.
renamed schedule to poll_rate and changed logic to operate identically to poll_rate in the top level configuration.
Qinusty
force-pushed
the
qinusty/per-feed-polling
branch
2 times, most recently
from
58b41ff to
06a9bf2
Compare
Qinusty
force-pushed
the
qinusty/per-feed-polling
branch
from
06a9bf2 to
c1dddc0
Compare
This follows on from #85 to introduce separate polling timers for individual feeds.
Feeds are grouped and polled based on their schedules defined in FeedOptions, alternatively a default schedule is applied based upon pollRate in the root of the configuration (which runs if
timeris enabled in the configuration).