Skip to main content

Introduction

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

Installation

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:

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

[bluebream]
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:

[buildout]
develop =
    src/my.package

[bluebream]
eggs =
    my.package

Configuration

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.

bluebream.ini

Cut/paste, save as bluebream.ini:

[loggers]
keys = root, wsgi

[handlers]
keys = console, accesslog

[formatters]
keys = generic, accesslog

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

[formatter_accesslog]
format = %(message)s

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

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

[logger_root]
level = INFO
handlers = console

[logger_wsgi]
level = INFO
handlers = accesslog
qualname = wsgi
propagate = 0

[filter:translogger]
use = egg:Paste#translogger
setup_console_handler = False
logger_name = wsgi

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

[app:zope]
use = egg:collective.recipe.bluebream
filter-with = translogger

[server:main]
use = egg:Paste#http
host = 127.0.0.1
port = 8080

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

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

<zodb>

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

# 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>
</zodb>

<eventlog>
  # 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.

  <logfile>
    path z3.log
    formatter zope.exceptions.log.Formatter
  </logfile>

  <logfile>
    path STDOUT
    formatter zope.exceptions.log.Formatter
  </logfile>
</eventlog>

#developer mode
devmode on

Execution

Now you can run paster:

$ bin/paster serve bluebream.ini

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

Completion

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

Changelog

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]

Metadata

Release files for collective.recipe.bluebream 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for collective.recipe.bluebream 0.4.0
File Size Uploaded Provenance
collective.recipe.bluebream-0.4.0.zip 42.5 kB Without provenance Details

Release files / collective.recipe.bluebream-0.4.0.zip

Download URL collective.recipe.bluebream-0.4.0.zip
Size 42.5 kB
Tags Source
SHA-256 checksum
How to use checksums
b3c77d1c45d1164d30572c236a6566aff9e5ffde2fd526db12a2ca0b4906c04a
BLAKE2b-256 checksum
How to use checksums
36a6421008e1502657df2123dadf998c0d085a68a6f793cdd397634d3559daa6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for collective.recipe.bluebream 0.4.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page