[Grok-dev] SVN Deployment

[Uli Fouquet]

Hi there,

Tim Cook wrote:
> The document at
> http://grok.zope.org/documentation/how-to/placing-your-grok-project-under-version-control 
> 
> used to be correct and was very helpful.
> 
> Now with Grok 1.0a2  we have many issues with deploying an application
> via SVN.  There seems to be hard coded paths in many places and I can't
> find a tool or switch on a tool that will fix them.

Thanks for spotting this, Tim!

This looks like a serious issue to me. Many of the configuration files
in etc/ contain hardcoded paths and it looks difficult to (re)generate
them using existing buildout-recipes (which would be the first solution
I would think of).

Generating those files with `grokproject` only (and thus defining
hardcoded paths) looks like a real bug to me.

I _think_ the better way would be to have something like this in
buildout.cfg::

  [buildout]
  develop = .
  parts = ... configfiles

  [configfiles]
  recipe = z3c.recipe.textfile
  path = etc
  zope.conf = site-definition ${buildout:directory}/etc/site.zcml
      <zodb>
      ...
  
  site.zcml = <configure />
  ...

or similar, so that all those configuration files could be recreated by
different developers with their local environments (paths, most notably)
applied.

Unfortunately a buildout-recipe like the one above seems not to exist in
PyPI although it looks quite useful to me. Therefore I started to create
one. It should be available later today. Is there already a recipe we
could use in that case?

Afterwards we might rethink the way, grokproject creates those files.

I filed a bug report for this:

  https://bugs.launchpad.net/grok/+bug/325299

Best regards,

-- 
Uli

-------------- 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/20090204/f09a0daa/attachment-0001.bin