# HG changeset patch
# User ymh <ymh.work@gmail.com>
# Date 1371441255 -7200
# Node ID 2a820542808c93490c89cf300f247f916d1c1755
# Parent  3799e12bdba34a3dba7b48ff7d29a0b1ffb088e4
restore wsgi app

diff -r 3799e12bdba3 -r 2a820542808c src/jocondelab/wsgi.py
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/src/jocondelab/wsgi.py	Mon Jun 17 05:54:15 2013 +0200
@@ -0,0 +1,33 @@
+"""
+WSGI config for jocondelab 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"] = "jocondelab.settings"
+os.environ.setdefault("DJANGO_SETTINGS_MODULE", "jocondelab.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)
+