summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/toaster/toastermain/wsgi.py
diff options
context:
space:
mode:
authorAlexandru DAMIAN <alexandru.damian@intel.com>2013-10-11 13:46:23 +0100
committerAlexandru DAMIAN <alexandru.damian@intel.com>2013-10-16 15:26:37 +0100
commitcb1338dedc3873ac81488df9dd3aa6f048e6b02f (patch)
treec94cfe05a88b87bcd8cda1ae5b825ac475601b80 /bitbake/lib/toaster/toastermain/wsgi.py
parentfaf8f8660fae26a14578738b642fdeb08bcb9d54 (diff)
downloadpoky-cb1338dedc3873ac81488df9dd3aa6f048e6b02f.tar.gz
bitbake: add toaster code to bitbake
This patch adds the Toaster component to Bitbake. Toaster is a module designed to record the progress of a Bitbake build, and data about the resultant artifacts. It contains a web-based interface and a REST API allowing post-facto inspection of the build process and artifacts. Features present in this build: * toaster start script * relational data model * Django boilerplate code * the REST API * the Simple UI web interface This patch has all the development history squashed together. Code portions contributed by Calin Dragomir <calindragomir@gmail.com>. Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>
Diffstat (limited to 'bitbake/lib/toaster/toastermain/wsgi.py')
-rw-r--r--bitbake/lib/toaster/toastermain/wsgi.py32
1 files changed, 32 insertions, 0 deletions
diff --git a/bitbake/lib/toaster/toastermain/wsgi.py b/bitbake/lib/toaster/toastermain/wsgi.py
new file mode 100644
index 0000000000..6277eb4d5e
--- /dev/null
+++ b/bitbake/lib/toaster/toastermain/wsgi.py
@@ -0,0 +1,32 @@
1"""
2WSGI config for Toaster project.
3
4This module contains the WSGI application used by Django's development server
5and any production WSGI deployments. It should expose a module-level variable
6named ``application``. Django's ``runserver`` and ``runfcgi`` commands discover
7this application via the ``WSGI_APPLICATION`` setting.
8
9Usually you will have the standard Django WSGI application here, but it also
10might make sense to replace the whole Django WSGI application with a custom one
11that later delegates to the Django one. For example, you could introduce WSGI
12middleware here, or combine a Django application with an application of another
13framework.
14
15"""
16import 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["DJANGO_SETTINGS_MODULE"] = "Toaster.settings"
22os.environ.setdefault("DJANGO_SETTINGS_MODULE", "toastermain.settings")
23
24# This application object is used by any WSGI server configured to use this
25# file. This includes Django's development server, if the WSGI_APPLICATION
26# setting points here.
27from django.core.wsgi import get_wsgi_application
28application = get_wsgi_application()
29
30# Apply WSGI middleware here.
31# from helloworld.wsgi import HelloWorldApplication
32# application = HelloWorldApplication(application)