[Grok-dev] SVN Deployment

[Uli Fouquet]

Hi Michael,

Michael Haubenwallner wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Uli Fouquet wrote:
> > 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).
> 
> Don't get what you mean -- with the current zopectl layout (grok-0.14)
> you have parts/zopectl/zope.conf and site.zcml. They too have all
> hardcoded paths.

Yep, but these files are generated by a buildout recipe. Every
developer running bin/buildout gets his/her local paths in this files.
In this sense the paths are not hardcoded. This is not true for the
current files in etc/.

Wicherts recipe could help us out of this :-)

> If you are talking about this:
>   grokproject --svn-repository=REPOS
> 
> You could be right, adjusting that to ignore the etc folder or parts of
> it would be next on the list.

That would also be necessary, right. Good, you mention it :-)

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/fd393a31/attachment.bin