Should I use the newly stable asgi workers for a Django ASGI server? #3524
Unanswered
arthurnalves
asked this question in
Q&A
Replies: 1 comment
-
|
The asgi worker currently does not handle all exceptions triggered from parser code, so it will not respond to some requests. Depending on what reverse proxy your application is sitting behind, using the asgi worker right now could lead to delayed and/or less useful error responses. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've been running an ASGI Django server (with Django Channels for websockets) with the combo Gunicorn+Uvicorn, as per suggested by Django itself.
https://docs.djangoproject.com/en/6.0/howto/deployment/asgi/uvicorn/#deploying-django-using-uvicorn-and-gunicorn
Given that, as of 25.1.0, ASGI workers are considered stable (https://gunicorn.org/2026-news/#changes), are there any recommendations on using them directly for my Django server and ditchiing Uvicorn?
Beta Was this translation helpful? Give feedback.
All reactions