samdolan805

3 ms·

1. 1.▲
   by samdolan805 11y ago

   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 s
2. 2.▲
   by samdolan805 11y ago

   Shouldn't be too hard. I threw in an issue to track it: https://github.com/ajvb/kala/issues/41
3. 3.▲
   by samdolan805 11y ago

   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 e
4. 4.▲
   by samdolan805 11y ago

   Can you start an issue so we can start discussing what this would look like? What kind of APIs would you need for this?
5. 5.▲
   by samdolan805 11y ago

   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, bu