Yet another introduction to zc.buildout.

Lightning-talk for DjangoCon-Toulouse 2012, by Benoît Bryon.

Slides available at http://tech.novapost.fr

Have you ever...

• executed commands
• shared them as a script
• made the script configurable to support several environments...
• ... and even more configurable to support several projects
• released all this work publicly
• accepted third-party plugins

• core provides configuration parser and recipes runner
• recipes are deployment scripts (install, uninstall, update)
• extensions are pluggable batteries

[buildout]
parts =
    hello-world
    activate

[hello-world]
recipe = z3c.recipe.usercrontab
times = 0 7 * * *
command = echo "Hello world"

[activate]
recipe = evg.recipe.activate

Many recipes are available on PyPI

[buildout]
parts = someproject

[someproject]
recipe = z3c.recipe.scripts
eggs =
    bpython
    Sphinx
    someproject
include-site-packages = True
allowed-eggs-from-site-packages = lxml

Have a look at generated scripts in bin/ folder: per-script sys.path tuning.

• Repeatable: configuration-driven
• Predictable: does what is expected, or reports errors
• Extensible: extensions and recipes are Python packages
• Isolated: everything lives in workspace
• Portable: Python

Great for teams and open-source projects.

• Deploy Python environments
• on local machines
• with a single user

Run buildout in your (make/fabric/salt/chef/puppet) deployment strategy.

• Online documentation
• Useful links
• My 2 cents

Recipes or extensions you'll like

• z3c.recipe.scripts
• isotoma.recipe.django
• mr.developer
• collective.recipe.omelette
• buildout-versions or buildout.dumppickedversions