From 03c9d0b595432c19f6a5351570f19b99d417ac25 Mon Sep 17 00:00:00 2001 From: Filipp Lepalaan Date: Thu, 4 Jul 2013 00:15:35 +0300 Subject: Initial commit --- motor/wsgi.py | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 motor/wsgi.py (limited to 'motor/wsgi.py') diff --git a/motor/wsgi.py b/motor/wsgi.py new file mode 100644 index 0000000..374756b --- /dev/null +++ b/motor/wsgi.py @@ -0,0 +1,32 @@ +""" +WSGI config for motor 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 + +# We defer to a DJANGO_SETTINGS_MODULE already in the environment. This breaks +# if running multiple sites in the same mod_wsgi process. To fix this, use +# mod_wsgi daemon mode with each site in its own daemon process, or use +# os.environ["DJANGO_SETTINGS_MODULE"] = "motor.settings" +os.environ.setdefault("DJANGO_SETTINGS_MODULE", "motor.settings") + +# 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() + +# Apply WSGI middleware here. +# from helloworld.wsgi import HelloWorldApplication +# application = HelloWorldApplication(application) -- cgit v1.2.3