umputun / cronn Goto Github PK

The current implementation of email notification is somewhat similar to a subset of https://github.com/go-pkgz/notify functionality. It was implemented prior, and notify was inspired by this thing (or a similar one).

It will be nice to remove it and migrate to the go-pkgz/notify first. This step won't add any new functionality but will remove the local email part of the notify package and simplify the code. The second step may add more notification destinations.

In many cases running the same job as the previous job still running is something unexpected and should be avoided. The easiest solution is to add some --no-dup parameter and postpone or even reject scheduled job in such cases.

I'm not sure if such a simple limiter will be granular enought and can imagine jobs we want to run in parallel and some we don't.

Currently, templates are hardcoded. It could be used as defaults but we need the ability to redefine it with user's files

The goal is to build (as a part of ci pipeline) deb and/or rpm packages installing cronn service (systemd?).

By default, all output goes to stdout/stderr. It will be nice to have an option to redirect outputs to a log file. Not sure if we want a single log for all tasks or log per job. In the case of a single log, it makes sense to add some job prefix to each line.

In case if cronn runs without --update flag we want to support sighup to initiate reload.