[Grok-dev] buildout.cfg

Wichert Akkerman wichert at wiggy.net
Thu Jul 16 07:17:12 EDT 2009

On 7/16/09 12:09 PM, Hendrik Bunke wrote:
> --On Thu, 16 Jul 2009 11:55, Sebastian Ware wrote:
>> My bad, I realise now that buildout.cfg shouldn't be version
>> controlled, or at least not shared between dev and prod server.
> I have no experience with grok buildouts, but why don't you use a
> second .cfg for deployment (e.g.  deployment.cfg)? It just needs
> [buildout]
> extends =
>      buildout.cfg
> and your overrides. You could then run buildout with option '-c
> deployment.cfg' on your production server. And, of course, both
> .cfg could and should be under version control.

I am just starting to use a slightly different approach: I have a single 
base.cfg, and separate production.cfg and devel.cfg files for the 
production and development environments. That way if I run bin/buildout 
and forget the -c parameter (which happened way too often) I get an 
error message instead of suddenly turning a production environment into 
a devel environment or the other way around.


More information about the Grok-dev mailing list