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
{{ message }}
This repository has been archived by the owner. It is now read-only.
I'm opening this as a call for users to come out and "make their case", so to speak. Given increased understanding of how Celery is used, the consensus appears to be coming back to this image not holding much value by itself, and there being more value in folks embedding Celery in their application containers directory (exactly like Sentry does, for example).
If I've got some gross misunderstanding of how Celery is supposed to be used, I'd love to see some documentation to help me understand. 😇 ❤️
The text was updated successfully, but these errors were encountered:
See also docker-library/docs#630 for the deprecation of Django, which I think Celery is similar to in the way that it's expected to be used (as part of an application, not as a standalone tool).
I'm opening this as a call for users to come out and "make their case", so to speak. Given increased understanding of how Celery is used, the consensus appears to be coming back to this image not holding much value by itself, and there being more value in folks embedding Celery in their application containers directory (exactly like Sentry does, for example).
If I've got some gross misunderstanding of how Celery is supposed to be used, I'd love to see some documentation to help me understand. 😇 ❤️
The text was updated successfully, but these errors were encountered: