lally elias

We can use v1 branch

@rturk 1. We have to extract codes that seems to be usable as stand alone kue utility extensions like [cleanup](https://github.com/lykmapipo/kue-scheduler/blob/master/index.js#L1326) which on my side i found to reuse it all...

@rturk 2. Allow for multi-process scheduler i.e having other instance to process the work and other instance to schedule the work to address #76 and use #72 as start point...

@rturk 3. Improve test coverage and code comments as well as user guides. Test coverage may be aimed at unit testing which is not well addressed by now

Any one with features that seems to miss we can discuss here for v1 Thanks all.

4. Implent UI for `kue-schedule` similar to one that is used by kue. This may be extending existing kue ui.

@KeKs0r Currently `every` jobs have not been integrated with kue ui. Only `schedule` and `once` job have been intergrated. Am open for discussion

@KeKs0r - `schedule` just use `kue delay` and `once` just save a job directlty. - [`every`](https://github.com/lykmapipo/kue-scheduler/blob/master/index.js#L535) uses `redis key expiry`. - first if job is checked if is [unique and...

@KeKs0r That sound cool. Let me review the codes by this weekend and see what can be done. :100:

@KeKs0r Can we work on this feature together. I will appreciate a discussion around it.