mirror of
https://github.com/zulip/zulip.git
synced 2025-10-27 18:13:58 +00:00
20dcc2e036
Because import_module does not correctly handle safe circular imports we need to import zerver.models first before the middleware tries to import it. (imported from commit 1afebd8c950c44c8d136b0b63a09319ccef02555)
30 lines
1.2 KiB
Python
30 lines
1.2 KiB
Python
"""
|
|
WSGI config for zulip 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.
|
|
|
|
"""
|
|
import os
|
|
|
|
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "zproject.settings")
|
|
|
|
# Because import_module does not correctly handle safe circular imports we
|
|
# need to import zerver.models first before the middleware tries to import it.
|
|
|
|
import zerver.models
|
|
|
|
# This application object is used by any WSGI server configured to use this
|
|
# file. This includes Django's development server, if the WSGI_APPLICATION
|
|
# setting points here.
|
|
from django.core.wsgi import get_wsgi_application
|
|
application = get_wsgi_application()
|