Is this project deprecated?

[liquidpele]

@auvipy Hey, questions about this project... is this completely replaced by django-celery-beat and django-celery-results at this point? The docs seem to suggest this, but don't outright say it.

[liquidpele]

It looks like there is a monitoring capability of it, which someone forked and made celery4 compatible here: https://github.com/jezdez/django-celery-monitor

I suppose that functionality is also covered by flower though? https://github.com/mher/flower

I'd like to know more about the the decisions made around this and what the plans are for the future. I think it would be nice to have monitoring capabilities built-in, but maybe there were reasons why that was not done like it was for beat and results?

[auvipy]

It is deprecated for celery 4. and yes monitor is forked by another guy. Though the flower is the suggested one. The goal is two make the two new package as complete and futuristic as possible. And docs might need some good amount of edits as well

[hvitis]

@auvipy so this is not compatible with eg Django 2.2 ? I´ve seen a ticket for bumping the version up. In case I want to use celery with Django I still can use the official guide for "manual" connecting right?

https://docs.celeryproject.org/en/stable/django/first-steps-with-django.html

[auvipy]

with celery 4.x series django-celery-beat, and django-celery-result should be used.