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

Create getting_started.rst #328

Merged
merged 1 commit into from
Jul 7, 2022

Conversation

valberg
Copy link
Contributor

@valberg valberg commented Jul 7, 2022

Trying to clear up the confusion from #326

Rendered it looks like this:

image

@valberg
Copy link
Contributor Author

valberg commented Jul 7, 2022

@AmitPhulera What do you think?

@AmitPhulera
Copy link
Contributor

This looks good @valberg 🎉
Thanks for adding these.

@auvipy auvipy merged commit e90771f into celery:master Jul 7, 2022
@tisdall
Copy link

tisdall commented Jul 22, 2022

I know this is copied from the celery docs, but I'm wondering if CELERY_CACHE_BACKEND = 'django-cache' is actually correct... It seems like you need to use CELERY_RESULT_BACKEND = 'django-cache' to tell it to use the cache backend defined in django-celery-results and then CELERY_CACHE_BACKEND to specify which cache to use.

Regardless of the above, it might be good to include the CELERY_RESULT_EXTENDED documentation here too: https://docs.celeryq.dev/en/stable/django/first-steps-with-django.html

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

Successfully merging this pull request may close these issues.

None yet

4 participants