[Grok-dev] buildout-generated config files in grokproject

Uli Fouquet uli at gnufix.de
Thu Feb 5 07:38:12 EST 2009

Hi there,

Just committed some changes into the grokproject-trunk that care for
configuration files (i.e. the files in etc/ dir of a grok project) to be
generated by ``zc.buildout`` (using Wicherts buildout-recipe) instead of
being generated by grokproject itself. 

This is, of course, not released yet.

Projects now have a new subdirectory ``cfg_templates`` where all the
templates for the configuration files are stored::

     + etc/  (now empty before running buildout)
     + cfg_templates/
          + README.txt (tells what purpose files in this dir have)
          + deploy.ini.in
          + debug.ini.in
          + site.zcml.in
          + zope.conf.in
          + zdaemon.conf.in
     + buildout.cfg
     + setup.py

When running ``bin/buildout`` in a project, the templates are parsed,
paths replaced according to the local environment and written to etc/.

Before finishing this task, I would like to know, what you think about 

* the template directory being placed in the project root (could there 
  be a better place?),

* the name of the directory (could there be a shorter name?)

* the set of config files stored (only zope.conf, zdaemon.conf have 
  paths replaced; the other templates are copied as-is)

Best regards,


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20090205/fe84bbb7/attachment-0001.bin 

More information about the Grok-dev mailing list