[Grok-dev] Copying a grok installation to another machine
zedobject at gmail.com
Thu Sep 10 07:51:57 EDT 2009
My problem is much simpler! To save time, I wish to transfer my bare grok
installation using a memory stick to a bare python (equipped with
setuptools and pywin32) on another machine with identical OS. Instead of
doing "easy_install grokproject" from the internet. I am sorry if my
original request was misleading.
About transerring a specific grok application, oddly, I had not thought
much. I had reasoned that when need appears, since it is a valid Zope
application, I should be able to use Zope's export feature. (( But Hark!!
Probably I am talking about Zope2, not Zope3. Sorry.))
Thanks and regards
On Wed, Sep 9, 2009 at 7:40 PM, Uli Fouquet <uli at gnufix.de> wrote:
> Hi Sebastian,
> Sebastian Ware wrote:
> > I might have an old grokproject on my dev machine because I found a
> > hardcoded absolute path in bin/buildout.
> We all have 'hardcoded' paths in bin/buildout (at least I think so).
> Even with the newest grok/grokproject. But the bin/buildout script is
> recreated with values from your very local system when running:
> $ my-python-to-use-with-grok bootstrap.py
> in your grokproject. If you do not have bootstrap.py installed in your
> project root (grokproject should have generated one), you can get it
> (or, if you host your project on SVN, you might add an external
> reference to the bootstrap dir:
> which will generate bootstrap/bootstrap.py in your local project root)
> So after copying a project from one machine to another, at least these
> _both_ steps are required:
> 1) run 'python bootstrap.py' *and*
> 2) run 'bin/buildout' afterwards.
> Best regards,
> Grok-dev mailing list
> Grok-dev at zope.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Grok-dev