Skip to main content
Help us improve Python packaging – donate today!

zc.buildout recipe to install static resources using Twitter Bower.

Project Description

Introduction

This recipe allows downloading and installing assets such as images, CSS and JavaScript using Twitter Bower.

Supported options

The recipe supports the following options:

packages

Packages that should be installed with bower. Packages specified here are passed to bower verbatim. They can be specified in any form that is supported by bower:

packages =
    underscore
    git://github.com/components/jquery.git
    bootstrap#2.2.2
base-directory

Absolute path to the bower “project” directory. bower install is run from this directory and the bower configuration file, .bowerrc is also placed here. Optional; defaults to ${buildout:parts-directory}/bower. Requires an absolute path.

This directory is not removed when the Buildout part is uninstalled.

executable
Absolute path to the bower executable. Packages are installed using this executable. Optional; defaults to bower on PATH.
downloads

Relative path, from the base-directory, to the directory where bower will download packages to. This path is written to the .bowerrc file prior to running the executable. Optional; defaults to downloads. Thus, the downloaded packages are placed in ${base-directory}/downloads by default.

This directory is removed when the Buildout part is uninstalled.

Example usage

A sample buildout that uses this recipe could look like:

[buildout]
parts = node web

[node]
recipe = gp.recipe.node
url = http://nodejs.org/dist/v0.8.16/node-v0.8.16.tar.gz
npms = bower@0.6.8
scripts = bower

[web]
recipe = bowerrecipe
packages = jquery#1.8.3 normalize-css
executable = ${buildout:bin-directory}/bower

This would place the downloaded packages in parts/bower/downloads. Modifying the web section to be:

[web]
recipe = bowerrecipe
packages = jquery#1.8.3 normalize-css
executable = ${buildout:bin-directory}/bower
base-directory = ${buildout:parts-directory}
downloads = components

would result in bower placing the downloaded packages in parts/components.

Notes

  1. Bower still looks at the ~/.bowerrc file. Hence, if this file exists, it may affect the buildout bower configuration
  2. Bower still uses the cache located in the user’s home directory. For me, this happens to be ~/.bower/cache/

Contributors

Anshuman Bhaduri Sebastian Wehrmann

Changelog

0.2

  • Fix removal of base directory upon uninstall. (#1)
  • Update files on every buildout run, rather loading them once.

0.1.1

  • Fixed documentation so it displays correctly on PyPI [Anshuman Bhaduri]

0.1

  • Created initial recipe [Anshuman Bhaduri]

Release history Release notifications

This version
History Node

0.2

History Node

0.1.1

History Node

0.1

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Filename, size & hash SHA256 hash help File type Python version Upload date
bowerrecipe-0.2.tar.gz (5.1 kB) Copy SHA256 hash SHA256 Source None Jun 14, 2015

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging CloudAMQP CloudAMQP RabbitMQ AWS AWS Cloud computing Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page