samdolan805

Feel free to throw issues into the GH tracker so we can get them on the roadmap.

My initial use case for this is for complicated time-based triggers that would be an absolute PITA/impossible to model in cron. We both felt the pain of setting up celery, etc.; @ajvb took that pain and put this together.

Shouldn't be too hard. I threw in an issue to track it: https://github.com/ajvb/kala/issues/41

We work together there. We actually both started working on a job scheduler independently, but joined forces and he ran with it. It's @ajvb's personal project, but we'll be using it at 222 labs for sure. You can shoot me an email at my username without the numbers @ gmail.com and I'll hook in @ajvb to the thread.

Can you start an issue so we can start discussing what this would look like? What kind of APIs would you need for this?

I work with @ajvb. We'll be working on getting this into production over the next 2 months. To do so, we'll be working on adding redis as a backend and making it distributable. The goal is to make it really easy to get started, but be able to scale out to bigger production systems easily.

@ajvb has plans for an awesome dashboard as well to complement this :) Stay tuned... good things ahead.