On Thu, Dec 15, 2011 at 1:41 PM, Stephan Richter <stephan.richter@gmail.com> wrote:

On Thursday, December 15, 2011 12:59:57 PM Jim Fulton wrote:

...

So, does anyone know of a recipe, similar to zc.zope3recipes:instance that drives this?

I am using collective.recipe.template to generate different configuration files from a common template. Here is a snippet from my buildout file:

[DEFAULT] input = ${buildout:paster-directory}/dev.ini.in output = ${buildout:paster-directory}/dev.ini sites-config-directory = ${buildout:directory}/data/sites-config/dev mail-directory = ${buildout:var-directory}/mail zodb-config-path = ${buildout:paster-directory}/zodb.conf database = db database-host = localhost logs-directory = ${buildout:directory}/logs web-server-host = localhost web-server-port = 8000

[dev_ini] recipe = collective.recipe.template call-server = http://localhost:8000/calls/tropo

[staging_ini] recipe = collective.recipe.template input = ${buildout:paster-directory}/prod.ini.in output = ${buildout:paster-directory}/staging.ini web-server-host = staging web-server-port = 8020 database = staging-db

How do values get from DEFAULT into the other sections? If this is a buildout behavior, it's unintentional and unlikely to work in the future. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton