Welcome, guest | Sign In | My Account | Store | Cart

Notice! PyPM is being replaced with the ActiveState Platform, which enhances PyPM’s build and deploy capabilities. Create your free Platform account to download ActivePython or customize Python with the packages you require and get automatic updates.

pypm install collective.recipe.bluebream

How to install collective.recipe.bluebream

  1. Download and install ActivePython
  2. Open Command Prompt
  3. Type pypm install collective.recipe.bluebream
 Python 2.7Python 3.2Python 3.3
Windows (32-bit)
0.4.0 Available View build log
0.3.0 Available View build log
Windows (64-bit)
0.4.0 Available View build log
0.3.0 Available View build log
Mac OS X (10.5+)
0.4.0 Available View build log
0.3.0 Available View build log
Linux (32-bit)
0.4.0 Available View build log
0.3.0 Available View build log
Linux (64-bit)
0.4.0 Available View build log
0.3.0 Available View build log
Lastest release
version 0.4.0 on May 23rd, 2012


collective.recipe.bluebream is a zc.buildout recipe you can use to bootstrap a Bluebream project. It does the following:

  • Requires the packages required by BlueBream (according to the sample project setup described here: http://bluebream.zope.org/doc/1.0/gettingstarted.html)
  • Installs bin/paster
  • Installs a small WSGI application
  • Installs ZCML configuration files
  • Adds some var directories if they do not exist
  • Supports develop eggs


Create a buildout:

$ virtualenv-2.7 .
$ bin/pip install zc.buildout
$ bin/buildout init

Then edit buildout.cfg; use collective.recipe.bluebream like any recipe: just add a part and configure the recipe parameter. You should also configure a known good set of packages via the extends parameter:

extends = http://download.zope.org/bluebream/bluebream-1.0.cfg
parts =
versions = versions

recipe = collective.recipe.bluebream

Then run buildout:

$ bin/buildout
Develop eggs

As of version 0.3.0, collective.recipe.bluebream supports package development via the eggs parameter:

develop =

eggs =


You should now have a bin/paster script. To run bluebream, you will also need a WSGI configuration file and a Zope configuration file. Here are some sample configuration files to get you started.


Cut/paste, save as bluebream.ini:

keys = root, wsgi

keys = console, accesslog

keys = generic, accesslog

format = %(asctime)s %(levelname)s [%(name)s] %(message)s

format = %(message)s

class = StreamHandler
args = (sys.stderr,)
level = ERROR
formatter = generic

class = FileHandler
args = ('access.log', 'a')
level = INFO
formatter = accesslog

level = INFO
handlers = console

level = INFO
handlers = accesslog
qualname = wsgi
propagate = 0

use = egg:Paste#translogger
setup_console_handler = False
logger_name = wsgi

# Change the last part from 'ajax' to 'pdb' for a post-mortem debugger
# on the console:
use = egg:z3c.evalexception#ajax
next = zope

use = egg:collective.recipe.bluebream
filter-with = translogger

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

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

Cut/paste, save as zope.conf:

# main zope configuration file for debug mode

# Identify the component configuration used to define the site:
site-definition bluebream.zcml


    path var/filestorage/Data.fs
    blob-dir var/blobstorage

# Uncomment this if you want to connect to a ZEO server instead:
#  <zeoclient>
#    server localhost:8100
#    storage 1
#    # ZEO client cache, in bytes
#    cache-size 20MB
#    # Uncomment to have a persistent disk cache
#    #client zeo1
#  </zeoclient>

  # This sets up logging to both a file and to standard output (STDOUT).
  # The "path" setting can be a relative or absolute filesystem path or
  # the tokens STDOUT or STDERR.

    path z3.log
    formatter zope.exceptions.log.Formatter

    path STDOUT
    formatter zope.exceptions.log.Formatter

#developer mode
devmode on


Now you can run paster:

$ bin/paster serve bluebream.ini

And open http://localhost:8080 in your browser.


That's it! Checkout http://bluebream.zope.org for more information about Bluebream.


0.4.0 - (2012-04-08)
  • Clean up package [aclark]
0.3.0 - (2011-07-27)
  • Support eggs parameter for develop eggs, etc. [aclark]
  • Add logger [aclark]
  • Add metadata to setup.py [aclark]
0.2.0 - (2011-07-27)
  • Create var dirs if they do not exist [aclark]
  • Include package data [aclark]
0.1.0 - (2011-07-27)
  • Initial release [aclark]

Subscribe to package updates

Last updated May 23rd, 2012

Download Stats

Last month:1

What does the lock icon mean?

Builds marked with a lock icon are only available via PyPM to users with a current ActivePython Business Edition subscription.

Need custom builds or support?

ActivePython Enterprise Edition guarantees priority access to technical support, indemnification, expert consulting and quality-assured language builds.

Plan on re-distributing ActivePython?

Get re-distribution rights and eliminate legal risks with ActivePython OEM Edition.