config package

Subpackages

• config.settings package
  • Submodules
  • config.settings.base module
  • config.settings.local module
  • config.settings.production module
  • config.settings.test module
  • Module contents

Submodules

config.api_router module

config.asgi module

ASGI config for SCRAM project.

It exposes the ASGI callable as a module-level variable named application.

For more information on this file, see https://docs.djangoproject.com/en/dev/howto/deployment/asgi/

config.consumers module

class config.consumers.TranslatorConsumer(*args, **kwargs)

Bases: AsyncJsonWebsocketConsumer

async connect()

async disconnect(close_code)

Called when a WebSocket connection is closed.

async receive_json(content)

Received a WebSocket message

async translator_add(event)

async translator_check(event)

async translator_remove(event)

async translator_remove_all(event)

class config.consumers.WebUIConsumer(*args, **kwargs)

Bases: AsyncJsonWebsocketConsumer

async connect()

async receive_json(content)

Called with decoded JSON content.

async wui_check_resp(event)

Forward a message to the correct Websocket.

config.routing module

config.urls module

config.websocket module

async config.websocket.websocket_application(scope, receive, send)

config.wsgi module

WSGI config for SCRAM project.

This module contains the WSGI application used by Django’s development server and any production WSGI deployments. It should expose a module-level variable named application. Django’s runserver and runfcgi commands discover this application via the WSGI_APPLICATION setting.

Usually you will have the standard Django WSGI application here, but it also might make sense to replace the whole Django WSGI application with a custom one that later delegates to the Django one. For example, you could introduce WSGI middleware here, or combine a Django application with an application of another framework.

Module contents