zerok / channels-in-docker Goto Github PK

Messages not showed in chat and server log:

combinedserver_1 | [2017/03/07 06:32:37] WebSocket DISCONNECT /socket [172.25.0.1:33257]
combinedserver_1 | [2017/03/07 06:32:39] WebSocket CONNECT /socket [172.25.0.1:33267]
combinedserver_1 | [2017/03/07 06:32:45] WebSocket DISCONNECT /socket [172.25.0.1:33261]
combinedserver_1 | [2017/03/07 06:32:53] WebSocket DISCONNECT /socket [172.25.0.1:33259]
combinedserver_1 | [2017/03/07 06:32:55] WebSocket CONNECT /socket [172.25.0.1:33270]

Run command:

docker-compose -f docker-compose.development.yml up

Production setup same result:

interfaceserver_1 | 172.25.0.1:52051 - - [07/Mar/2017:06:39:25] "GET /" 200 2641
interfaceserver_1 | 172.25.0.1:52057 - - [07/Mar/2017:06:39:25] "WSCONNECT /socket" - -
interfaceserver_1 | 172.25.0.1:52049 - - [07/Mar/2017:06:39:28] "WSDISCONNECT /socket" - -
interfaceserver_1 | 172.25.0.1:52043 - - [07/Mar/2017:06:39:28] "WSDISCONNECT /socket" - -
interfaceserver_1 | 172.25.0.1:52059 - - [07/Mar/2017:06:39:31] "WSCONNECT /socket" - -
interfaceserver_1 | 172.25.0.1:52053 - - [07/Mar/2017:06:39:36] "WSDISCONNECT /socket" - -
interfaceserver_1 | 172.25.0.1:52055 - - [07/Mar/2017:06:39:36] "WSDISCONNECT /socket" - -

Chrome Version 56.0.2924.76 (64-bit)

Hi. Why not use docker-compose entrypoint with the compose files? "Command"s are supposed to be overriden on need.

you may want to update your example to keep it up to date with the new architechture.

I am trying to learn django/docker and want to thank you for the example. Some things I am stumbling on and maybe you would like to add to future versions:

1. Serving static files (For some reason I find this extremely difficult using Django).
2. Configuring this example to run with nginx.

Thanks again!

We've been running Django Channels using a similar layout as this repository. In Channels 1.0, it was trivial to get a single container to run multiple workers because Channels 1.0 separated the request handling from the workers.

With the transition to Channels 2.0, this separation has gone away. The Channels documentation has an example of multiple workers using channels + nginx, but this configuration seems to require communication over a unix socket.

Do you have any thoughts on refining your example to show how to support multiple Daphne processes?

• Is this possible to use a unix socket when nginx is hosted in a sidecare container?
• If not, you would need a copy of nginx on the Daphne container to pull this off.
• Once you're running nginx on the Daphne container, it's pretty easy to serve static files as well.
• An nginx sidecar could still make sense for SSL termination, but may be unnecessary -- especially in cases like AWS ECS since the load balancer can do SSL termination.