39 lines
1.4 KiB
Python
39 lines
1.4 KiB
Python
#
|
|
# OtterTune - wsgi.py
|
|
#
|
|
# Copyright (c) 2017-18, Carnegie Mellon University Database Group
|
|
#
|
|
"""
|
|
WSGI config for the OtterTune website.
|
|
|
|
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
|
|
import sys
|
|
|
|
from django.core.wsgi import get_wsgi_application
|
|
|
|
|
|
sys.path.append('/var/www/ottertune')
|
|
sys.path.append('/var/www/ottertune/website')
|
|
|
|
# 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"] = "website.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.
|
|
application = get_wsgi_application() # pylint: disable=invalid-name
|