1 |
9668dad8
|
Frédéric Péters
|
"""
|
2 |
|
|
WSGI config for wcsinst project.
|
3 |
|
|
|
4 |
|
|
This module contains the WSGI application used by Django's development server
|
5 |
|
|
and any production WSGI deployments. It should expose a module-level variable
|
6 |
|
|
named ``application``. Django's ``runserver`` and ``runfcgi`` commands discover
|
7 |
|
|
this application via the ``WSGI_APPLICATION`` setting.
|
8 |
|
|
|
9 |
|
|
Usually you will have the standard Django WSGI application here, but it also
|
10 |
|
|
might make sense to replace the whole Django WSGI application with a custom one
|
11 |
|
|
that later delegates to the Django one. For example, you could introduce WSGI
|
12 |
|
|
middleware here, or combine a Django application with an application of another
|
13 |
|
|
framework.
|
14 |
|
|
|
15 |
|
|
"""
|
16 |
|
|
import os
|
17 |
|
|
|
18 |
|
|
# We defer to a DJANGO_SETTINGS_MODULE already in the environment. This breaks
|
19 |
|
|
# if running multiple sites in the same mod_wsgi process. To fix this, use
|
20 |
|
|
# mod_wsgi daemon mode with each site in its own daemon process, or use
|
21 |
|
|
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "wcsinst.settings")
|
22 |
|
|
|
23 |
|
|
# This application object is used by any WSGI server configured to use this
|
24 |
|
|
# file. This includes Django's development server, if the WSGI_APPLICATION
|
25 |
|
|
# setting points here.
|
26 |
|
|
from django.core.wsgi import get_wsgi_application
|
27 |
|
|
application = get_wsgi_application()
|
28 |
|
|
|
29 |
|
|
# Apply WSGI middleware here.
|
30 |
|
|
# from helloworld.wsgi import HelloWorldApplication
|
31 |
|
|
# application = HelloWorldApplication(application)
|