[Grok-dev] Copying a grok installation to another machine

Sebastian Ware sebastian at urbantalk.se
Wed Sep 9 08:40:03 EDT 2009

I might have an old grokproject on my dev machine because I found a  
hardcoded absolute path in bin/buildout.

Mvh Sebastian

On 8 sep 2009, at 15.16, Uli Fouquet wrote:

> Hi there,
> Sebastian Ware wrote:
>> You might have problems with this simplified approach if the  
>> filepaths
>> differ since they are hardcoded by grokproject in bin/buildout and  
>> the
>> other scripts in AppName/bin.
> This is actually not a problem, because the path in bin/buildout is
> rewritten when running bootstrap.py and the other paths of scripts in
> bin/ are then rewritten when running bin/buildout. grokproject itself,
> BTW, creates no hardcoded paths in bin/. They are all generated.
> That's one of the reasons we use buildout/setuptools :-)
> There might, however, remain some hardcoded paths in the configuration
> files, which depends indeed on the grokproject version you used when
> creating the project (and your manual modifications done afterwards to
> the setup).
> In next grokproject release we try to avoid hardcoded paths as good as
> possible, also in the config files.
> Best regards,
> -- 
> Uli

More information about the Grok-dev mailing list