Currently, when running the Django project with Docker and using Django Channels, we need to start the Django server with daphne (daphne -b 0.0.0.0 -p 8000 mesh.asgi:application) instead of the regular python manage.py runserver. This is because Django Channels requires running the ASGI server instead of the WSGI server.
daphne server does not support hot reloading on code changes, which makes the development workflow less efficient when working with Docker containers.
We need to explore better solutions to enable hot reloading for Django Channels when developing with Docker. Some potential solutions to consider is switching to watchgog or uvicorn
Currently, when running the Django project with Docker and using Django Channels, we need to start the Django server with
daphne
(daphne -b 0.0.0.0 -p 8000 mesh.asgi:application
) instead of the regularpython manage.py runserver
. This is because Django Channels requires running the ASGI server instead of the WSGI server.daphne
server does not support hot reloading on code changes, which makes the development workflow less efficient when working with Docker containers.We need to explore better solutions to enable hot reloading for Django Channels when developing with Docker. Some potential solutions to consider is switching to
watchgog
oruvicorn