You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
The --with-scheduler option is a great feature. and it has helped a lot in cases where the main scheduler fails.
I use django-rq-scheduler (the new repo) that relies on rq-scheduler for a few main functionalities. It could easily fallback to vanilla rq if some of the rq-scheduler functions are ported over rq.
(such as cron(), contains(), etc... )
The end goal is to avoid having a separate container (extra $$$) to run the scheduler only.
Thanks!
The text was updated successfully, but these errors were encountered:
Yes, that's the end goal. RQ also very recently gained a feature to track historical runs and results here so you can track the result of jobs that are run multiple times. #1725
Hi!
The --with-scheduler option is a great feature. and it has helped a lot in cases where the main scheduler fails.
I use django-rq-scheduler (the new repo) that relies on rq-scheduler for a few main functionalities. It could easily fallback to vanilla rq if some of the rq-scheduler functions are ported over rq.
(such as cron(), contains(), etc... )
The end goal is to avoid having a separate container (extra $$$) to run the scheduler only.
Thanks!
The text was updated successfully, but these errors were encountered: