-
Notifications
You must be signed in to change notification settings - Fork 12
Home
For installation and usage, see the readme
- RAM limit (perhaps free RAM limit)
-
env()
pattern match -- this would let you only run on certain machines, or restrict to anyENV
orSERVER
var ~preg_match('#app[0-4]#', env('machine_name'))
The next step would be to make it easy to make recurring tasks... when processed, tasks automatically reschedule themselves for their next run.
Recurring Tasks would live in a database, so it'd be nice to have some import/export/config, which could be committed with the code... (either that, or we automatically made Migrations for each entry)
We could put in some really basic reporting methods. These could be setup as a recurring task, and provide a window into "what happened" in a day/week/month ~ "total run tasks", "total successful tasks", "percent successful", "list all failed", "average execution time", "top 10 most often run tasks"....
It might be reasonable to expose Queue and QueueRecur via an admin CRUD web interface via the plugin. This wouldn't work for everyone, but it might be a helpful thing for some... ?