Scheduled events #26

New issue

Open

opened 2022-10-29 14:22:24 +00:00 by emacsen · 0 comments

emacsen commented

2022-10-29 14:22:24 +00:00

(Migrated from gitlab.com)

Once #25 is collecting stats, it would be nice to process this data on a regular basis.

For example, an email that goes out on regular intervals providing basic stats.

To do this, we need an abstraction around scheduling events. I haven't found a higher level of abstraction than ngx.timer.every but if we do, then we can use it, or we can write something very lightweight that provides some similar result- not all the way to cronjob level sophistication, but maybe something lighter.

An alternative might be to use ngx.timer.at, where the first timer is calculated, and then on process completion, a new nginx.timer.at is created.

Once #25 is collecting stats, it would be nice to process this data on a regular basis. For example, an email that goes out on regular intervals providing basic stats. To do this, we need an abstraction around scheduling events. I haven't found a higher level of abstraction than `ngx.timer.every` but if we do, then we can use it, or we can write something very lightweight that provides some similar result- not all the way to cronjob level sophistication, but maybe something lighter. An alternative might be to use `ngx.timer.at`, where the first timer is calculated, and then on process completion, a new `nginx.timer.at` is created.