[Zope3-dev] Re: Default zope.conf DB setup

[Christian Theune]

Gah.

Mea culpa.

Until recently I didn't know that the zope.conf.in could even be copied
over to zope.conf, because every checkout that I ever used always picked
up the zope.conf and nothing ever told me to copy it. (Although I was
slightly annoyed having to edit zope.conf.ing).

I'll check whether anyone reverted the changes yet, otherwise, I'll
clean that up.

(Luckily this only affects the checkouts, not the releases.)

On the other hand, I'd like to know whether I'm the only one who
stumbled over this, or if other people didn't know about copying
zope.conf.in before (Some people assume it's trivially obvious that if
it's named zope.conf.in then you know you have to copy it.)

*If* someone else had that problem too, I'd propose to change away from
the fallback of using zope.conf.in (we force people to create the
principals too, don't we?)

At gocept we historically had similar features in projects, but we never
fell back to using the '.in' version of a file but forced developers to
copy it. I can't remember any case where this ended up in accidential
checkins.

Sorry again,
Christian

Philipp von Weitershausen wrote:
> Stephan Richter wrote:
>> Hi everyone,
>>
>> I just noticed that zope.conf.in has now the following entry:
>>
>> <zodb>
>>   <demostorage>
>>   <zeoclient>
>>   server localhost:8100
>>   storage 1
>>   cache-size 20MB
>>   </zeoclient>
>>   </demostorage>
>> </zodb>
>>
>> This means that ZEO has to start up to run Zope after a default check
>> out/download. When I had no network connection in a hotel last week, I
>> could not start up Zope because ZEO would not get some network thing
>> going.
>> I think this is really unfortunate and I propose to change this back
>> to the old version:
>>
>> <zodb>
>>   <filestorage>
>>     path Data.fs
>>   </filestorage>
>> </zodb>
>>
>> Comments?
> 
> Yes, of course. It looks like Theuni accidentally committed his
> zope.conf.in in these revisions:
> 
>   http://svn.zope.org/?rev=69553&view=rev (3.3 branch)
>   http://svn.zope.org/?rev=69554&view=rev (trunk)
>   http://svn.zope.org/?rev=69599&view=rev (trunk)
> 
> These need to be reverted for zope.conf.in.
> 
> Christian, if you want to customize zope.conf.in, just copy it to
> zope.conf. That's why the file is suffixed with '.in' in the first place
> (fallback for when you don't have your own zope.conf).
> 
> Philipp
> _______________________________________________
> Zope3-dev mailing list
> Zope3-dev at zope.org
> Unsub: http://mail.zope.org/mailman/options/zope3-dev/ct%40gocept.com
> 

-- 
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: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : http://mail.zope.org/pipermail/zope3-dev/attachments/20060916/fd8034dd/signature.bin