BlueBream The Web Component Framework

9.9. Startup

9.9.1. Introduction

The BlueBream framework creates WSGI applications, which can run behind any WSGI compliant web servers. The main application is configured and created via a factory function defined inside This functions returns the WSGI complaint application object to the server. For example, in the “ticket collector” tutorial, you can see the factory function defined in src/tc/main/ file:


def application_factory(global_conf):
    zope_conf = global_conf['zope_conf']

PaseDeploy together with PasteScript are then used to run the WSGI application. However, any WSGI server can be used to run BlueBream application [1]. We provide PaseDeploy with the WSGI application factory as an entry point. For example, in the “ticket collector” tutorial, you can see the entry point defined in file:

main = tc.main.startup:application_factory

The application can now be launched as a web service using the paster serve command provided by PasteScript. To configure the web server, an INI file has to be passed to the command as an argument. The INI file defines the WSGI application, any WSGI middleware we may want and web server options. For example, in the “ticket collector” tutorial, you can see the WSGI application defined in deploy.ini file:

use = egg:ticketcollector

use = egg:Paste#http
host =
port = 8080

# set the name of the zope.conf file
zope_conf = %(here)s/etc/zope.conf

You can read more about PasteDeploy and PasteScript in the PythonPaste site.

9.9.2. Running WSGI application

When you run BlueBream application using the paster server command, you can see something like this:

$ ./bin/paster serve deploy.ini
Starting server in PID 13367.
serving on
[1]WSGI servers like mod_wsgi don’t require the paster serve command provided by PasteDeploy to run the WSGI server.
blog comments powered by Disqus

Table Of Contents

Previous topic

9.8. Configuration

Next topic

9.10. Functional Testing

This Page