[Grok-dev] Re: gocept.zope3instance

Christian Theune ct at gocept.com
Thu Jan 11 06:10:04 EST 2007


Hi,

Am Donnerstag, den 11.01.2007, 12:05 +0100 schrieb Philipp von
Weitershausen:
> Christian Theune wrote:
> > I've made a release of gocept.zope3instance today. I suggest we start
> > using that for our Zope instances.
> 
> Yes, it's very nice. I just tried it in my grok checkout (diff 
> attached). I especially like the ability to simply say "bin/instance fg" 
> to start the Zope 3 instance.
> 
> > I'm open for discussions about having more "default" profiles available
> > from the recipe, to allow smaller or larger chunks of zcml be loaded by
> > default.
> 
> I have two bug reports to make:
> 
> 1.) The advertised "user = user:passwd" doesn't work. Instead, it wants 
> "admin-user = user" and "admin-password = passwd". This isn't so much of 
> a bug as a documentation issue. Btw, it doesn't look like it supports 
> password managers for encrypted passwords. I wonder if 
> zc.recipe.zope3instance does...

Thanks. Updated in SVN.

> 2.) When the recipe fails, e.g. due to a missing configuration option in 
> buildout, it exits gracefully with a nice error message (I assume the 
> error message comes from zc.buildout). When you fix the problem in your 
> buildout.cfg and want to run the buildout again, gocept.zope3recipe 
> complains that it can't create the instance directory again. The problem 
> is this line:
> 
>          # XXX In theory we could just delete the parts directory here, 
> if it
>          # exists already. Or not?
>          os.mkdir(dest)

This is not so clear unfortunately, at least to me. I've gotta ask Jim
about what this means in buildout terminology ...

> When those problems are fixed, I'll be happy to commit my change.


> 
> einfaches Textdokument-Anlage (grok-gocept-instance.patch)
> Index: buildout.cfg
> ===================================================================
> --- buildout.cfg	(revision 71844)
> +++ buildout.cfg	(working copy)
> @@ -13,9 +13,11 @@
>  recipe = zc.recipe.filestorage
>  
>  [testinstance]
> -recipe = zc.recipe.zope3instance
> +recipe = gocept.zope3instance
>  database = testdata
> -user = grok:grok
> +admin-user = grok
> +admin-password = grok
> +address = 8080
>  eggs = setuptools
>         grok
>  zcml = zope.annotation
> @@ -40,9 +42,11 @@
>         grok-meta

Please notice, that the zcml option does not exist anymore. We have
created an approach where you can created a derived version of the ZCML
and add your pieces there. The exact structuring needs more discussion
though. Eventually we want to provide multiple profiles of skeletons in
the recipe. 

Christian

-- 
gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany
www.gocept.com - ct at gocept.com - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development
-------------- 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/20070111/f49905be/attachment.bin


More information about the Grok-dev mailing list