mirror of
https://git.yoctoproject.org/poky
synced 2026-02-07 09:16:36 +01:00
9501864db8
There are much better ways to handle this and most editors shouldn't need this in modern times, drop the noise from the files. Its not consitently applied anyway. (Bitbake rev: 5e43070e3087d09aea2f459b033d035c5ef747d0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
37 lines
1.4 KiB
Python
37 lines
1.4 KiB
Python
#
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
|
#
|
|
|
|
"""
|
|
WSGI config for Toaster 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"] = "Toaster.settings"
|
|
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "toastermain.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)
|