-
Notifications
You must be signed in to change notification settings - Fork 329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration with rq-scheduler? #70
Comments
What's the best way of making additional charts and tools pluggable? |
This would be fantastic. |
I agree 100% that this would be awesome. To avoid having a dependency on |
I think an "rq-scheduler-dashboard" should be a separate Flask blueprint from the current rq-dashboard, and should probably be a separate package at least initially. If rq-scheduler became closer to rq then this would motivate bringing the dashboards together too. But the fact that it was easy and clean to add the scheduler on top of rq says something. Basically I think each dashboard should be free to track the features of the corresponding underlying component. So if someone first made a standard alone scheduler dashboard in a separate Flask blueprint, we could then see how well the two sat next to one another before thinking about bringing them closer. It needs a first date!! |
* Summarises scheduled job count by queue * Lists scheduled jobs by queue * Tracks running status of scheduler Ref Parallels#70
I had a need for this as well so I took the changes from @helenst made in #95 and wrapped them up into a separate |
Can you provide a screenshot for this dashboard? |
@Docu Added a screenshot to the readme. |
Looks good, I also made some tweaks to the dashboard that I found useful (#94), it would be nice to harmonize and merge these improvements. Vincent transferred this repo to me, I would be happy to get things moving, pull requests are welcome. |
Closes Parallels#283 and closes Parallels#70
Hello,
Do you know if there is any work on integrating rq-dashboard with rq-scheduler? Would you accept a PR?
For instance, if a conditional import for
rq_scheduler
works, then a new section would be added to the web interface containing details on scheduled jobs. It would be optional.It may also be possible to take the blueprint from this package and use it in a new flask app that contains the rq-scheduler functionality (as a separate package or something, if you don't want rq-scheduler code to live in this project).
Anyway, just wanted to see what other folks thought, since it'd be nice to see both in one web interface.
The text was updated successfully, but these errors were encountered: