Table of contents

Django channels: channel layers, groups and users

Django channels: channel layers, groups and users

Channel layers allow you to interact and share information with different consumers in django channels. This allows each consumer to communicate with the rest. For example, when in a chat a user sends a message, everyone can read the message, when a user leaves a room, everyone can know that he left it. With this capability it is possible to create a distributed application in which information is shared among the different users.

If you don’t know what Django channels is, I recommend you to read my previous post, where I explain the basic parts of django channels: consumers, scope and events

Configure a channel layer

It is not enough for one instance to be able to access information from all other instances.

What if we want only some instances to have access to the information and not others?

Just as in a chat, you do not want all existing chats to receive your messages, nor do you expect to receive messages from all chats, only those in which you participate.

To handle this information in common we need a channel layer (an optional feature of django channels), and groups of channels or consumers. In this way we will ensure that each instance of a channel, that is, a consumer, can communicate with other channels, but not with all of them, only with those of the group we specify.

Channel layers under development

To use a channel layer in development we need to add an extra configuration to our configuration file and modify our consumer object. This configuration below tells Django to handle the channel layer in memory and is perfect for testing in development.

# mychannels/
    "default": {
        "BACKEND": "channels.layers.InMemoryChannelLayer"

Channel layers in production

The above configuration is not for production. For production we need to install redis and the channels-redis package. I told you a bit about redis when I explained how to create a history of products visited with django and redis.

sudo apt install redis
pip install channel-redis

If installed correctly we will have redis running on port 6379.

We will now directly access the redis application through its default port.

# mychannels/
    "default": {
        "BACKEND": "channels_redis.core.RedisChannelLayer",
        "CONFIG": {
            "hosts": [("", 6379)],

Broadcasting with a channel or consumer

After adding the above configuration, it is time to modify our consumer to send messages to the rest of the connections. In the previous post I explained that each consumer has the properties channel_layer and channel_name, which refer to the channel layer it belongs to and its own name, respectively. We will use those properties to get the channel layer it belongs to and its name.

Our consumer will continue to maintain its three main functions: connect, disconnect and receive, but with added functionality.

Schematic of groups and channel layers in django channels

The process by which a channel or consumer joins a group.

# chat/
import json
from channels.generic.websocket import WebsocketConsumer
from asgiref.sync import async_to_sync

class ChatConsumer(WebsocketConsumer):

    def connect(self):
        async_to_sync(self.channel_layer.group_add)("chat", self.channel_name)

    def disconnect(self, close_code):
        async_to_sync(self.channel_layer.group_discard)("chat", self.channel_name)

    def receive(self, text_data):
                    "type": "chat.message",
                    "text": text_data,

    def chat_message(self, event):

The changes we made were as follows:

  • We import the async_to_sync function, which allows us to execute asynchronous code synchronously.
  • We use the group_add method to add a channel (remember that a consumer is a representation of a channel) to a given group. That is, add the current channel/consumer to the group called “chat”. In the image above it is better explained.
  • In case a user disconnects, we remove it from the “chat” group with group_discard.
  • Now, every time we receive a message in a consumer, it will call the method group_send of the channel layer to which it belongs, which will be in charge of sending the data, in dictionary form, automatically to all the active members of the group “chat “.
  • The type key will tell the consumer which method to use. The syntax is replace the dot with an underscore. That is to say that the type chat.message will execute the chat_message method of each consumer that receives it.

Processing of a message from a websocket to a group of channel layers

Channel layer sending information to the group “chat” with its method group_send

Handling websockets in HTML

To simplify the connection to websocket in the browser, I’m going to take the Javascript code needed to send a message and place it in a super simple HTML template that will reside in templates/index.html. Create it if you don’t have it.

<!DOCTYPE html>
<html lang="en">
    <meta charset="UTF-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    // Se crea la conexión por websocket
    const chatSocket = new WebSocket(
            + '/ws/chat/'
    // Cada que se recibe un mensaje se lee y se imprime en pantalla
    chatSocket.onmessage = function(e) {
            const data = JSON.parse(;
    // Envia el texto "nuestro mensaje"
    function sendMessage() {
        let message = "nuestro mensaje"
            'message': message
    <button onclick=sendMessage()>Enviar</button>

The code is practically the same of the previous entry, I have only added the sending of the message to a function that will be executed when we press the button.

In our file of the chat app we create the view that is in charge of rendering the template

# chat/
from django.shortcuts import render

def useless_chat(request):
    return render(request, "index.html")

And let’s not forget to add this view to the urls of our project.

# mychannels/
from django.urls import path
from chat.views import useless_chat

urlpatterns = [
    path('chat/', useless_chat)

Ready! Now comes the interesting part… if you open two windows, two consumers will be created and every time a consumer sends a message, it will be received in the Django app and self.channel_layer.group_send will send it to the rest of the consumers, when they receive it, each consumer will execute its chat_message method, which will send the text that was sent.

Observe how both tabs receive the sent messages

Users in django channels

What about the users? So far we have been handling anonymous users. Note that authentication is quite simple in django channels. To incorporate it we wrap our application in the AuthMiddlewareStack middleware, django will handle the session object, as usual.

# mychannels/
import os

from channels.auth import AuthMiddlewareStack
from channels.routing import ProtocolTypeRouter, URLRouter
from django.core.asgi import get_asgi_application
import chat.routing

os.environ.setdefault("DJANGO_SETTINGS_MODULE", "mychannels.settings")

application = ProtocolTypeRouter({
  "http": get_asgi_application(),
  "websocket": AuthMiddlewareStack(

With this middleware we will have access to the user object through the scope in:

class ChatConsumer(WebsocketConsumer):

    def connect(self):
        async_to_sync(self.channel_layer.group_add)("chat", self.channel_name)
        self.user = self.scope["user"]
        self.send(text_data=json.dumps({"message": "Se ha conectado %s" % (self.user.username)}))

If you have a logged in user you will see something like this when logging in:

Django channels usuario loggeado

And if you are not logged in you will see an empty string, which corresponds to an anonymous user.

Anonymous user in Django channels

Login and logout in django channels

Django channels also provides us with functions to login and logout our users, just remember that the login function does not authenticate a user, it only logs them in, so the checks are up to you.

from asgiref.sync import async_to_sync
from channels.auth import login, logout, get_user

class ChatConsumer(WebsocketConsumer):


    def receive(self, text_data):
        async_to_sync(login)(self.scope, user)
        # La sesión se modifica con el login
        # Pero es necesario guardar la sesión 

    def disconnect(self, close_code):

Now you can complicate the sending of information so that it behaves the way you want it to, such as creating different rooms, or condition the sending of messages to a restricted group of users, or only to one of them.

Tips for django-channel production

Before deploying an application that involves channels I will tell you about the many things that can go wrong and how to prevent them.

django.core.exceptions.AppRegistryNotReady: Apps not loaded

If you are using uvicorn and an asgi application, this is because django tries to use applications that have not yet been loaded. To prevent the error manually load the application yourself before importing any other app.

In this particular case, the order of imports DOES matter.

from django.conf import settings
from django.core.asgi import get_asgi_application

current_settings = (
    "app.settings" if settings.DEBUG else "app.dev_settings"
os.environ.setdefault("DJANGO_SETTINGS_MODULE", current_settings)
django_asgi_app = get_asgi_application()

# el resto de tus imports van acá
# import app...

application = ProtocolTypeRouter(
        "http": django_asgi_app,
        # ...

Make sure you have the websocket libraries installed.

If you are going to work with websockets, make sure you have all the required libraries installed, uvicorn provides us with these libraries if we install its standard version.

pip install uvicorn[standard]

Otherwise we will get the error _[WARNING] No supported WebSocket library detected.

Make sure you are using the correct websocket protocol

The error can manifest itself in several ways, one of which is this deploys failing due to “unhealthy allocations”.

If you try to communicate with an insecure protocol to an insecure protocol you will get an error.

// Te toca definir la variable/funcion de manera dynamica
    ws_url = 'wss://...'
    ws_url = 'ws://...'
Eduardo Zepeda
Web developer and GNU/Linux enthusiast always learning something new. I believe in choosing the right tool for the job and that simplicity is the ultimate sophistication. I'm under the impression that being perfect is the enemy of getting things done. I also believe in the goodnesses of cryptocurrencies outside of monetary speculation.
Read more