Yep, you can do this over ASGI.

Thank you very much, I am happy to hear that. But I have heard on reddit that the server gets stuck when running command to run asgi server (gunicorn or daphne) to start channels. Is that still presists or it is fixed?

Have you tried it, and if so what errors are you receiving?

Actually I was deploying on anther service which was causing the server stuck situatuon while starting ASGI server and then I looked at reddit and saw that some of them was saying that it happen on Railway too. I will deploy in few hours and I will let you know.

@rc I am now deplying django-channels application for which I need to start asgi server to make channels work but When I set command in Procfile

web: daphne .asgi:application

then server is successfully started and showing

2024-01-07 08:44:25,699 INFO     Starting server at tcp:port=7097:interface=0.0.0.0

2024-01-07 08:44:25,699 INFO     HTTP/2 support enabled

2024-01-07 08:44:25,699 INFO     Configuring endpoint tcp:port=7097:interface=0.0.0.0

2024-01-07 08:44:25,700 INFO     Listening on TCP address 0.0.0.0:7097

but when I visit the website and try to connect with websocket like

const socket = new WebSocket(wss://:______.com:7097/ws/endpoint/);

then it is not connecting to websocket even after defining the port with wss.

^ For anyone curious, the question moved to this thread