Skip to content
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

Celery configuation #10

Closed
LianYangCn opened this issue May 9, 2018 · 1 comment
Closed

Celery configuation #10

LianYangCn opened this issue May 9, 2018 · 1 comment
Milestone

Comments

@LianYangCn
Copy link

README said:

# myproject/settings.py

CELERY_RESULT_BACKEND = BROKER_URL = 'redis://localhost:6379/1'

and

# myproject/celery.py
app.config_from_object('django.conf:settings')

So, celery will read RESULT_BACKEND which not set, then you can NOT get the celery task result or status.

Is that why you update the importing status by django.model?

In my opinion, celery.result is elegant and more faster to implement the importing status

Wish you and your project better!

@sheppard
Copy link
Member

Thanks for the feedback. The Celery configuration was meant as an example and certainly could be improved. The idea is to use the celery result backend for real-time updates but also log information in Django models (e.g. RunLog and Record) for later review.

Note that in the latest version of Django Data Wizard (1.1.0), celery is no longer the default backend.

@sheppard sheppard added this to the 1.1 milestone Feb 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants