On Tue, Dec 29, 2009 at 03:59:07PM +0000, Chris Withers wrote:
Marius Gedminas wrote:
Well. You didn't specify a database file in your zope,conf it seems. Without a declaration, there's no database.
Makes sense, in a rather user-unfriendly way. May I suggest the documentation be amended to supply a closer-to-working zope.conf? I'm referring to this bit:
http://docs.zope.org/zope2/releases/2.12/INSTALL.html#buildout-instances
where I didn't notice the word "starting" in "Create a Zope configuration file starting as follows".
Hmm, well, a full zope.conf is a bit bloated to go in those docs, which is why I worded it the way I did...
Is 46 lines too much? That's how much it takes to have python instancehome default-publisher-encoding # hm, what's this? first time I see one <eventlog> <logger access> <http-server> <zodb_db main> <zodb_db temporary> with a couple of %defines and comments. Or we could put a sample zope.conf somewhere on the web (heck, in svn is fine, using those nice *checkout* urls we've already used for downloading buildout's bootstrap.py or the Zope 2.12.2 versions.cfg). It'd be even better if there was a command I could run to generate an up-to-date default zope.conf, like mkzopeinstance does. Is there one? Maybe there's a place for "bin/zopectl init" that would mkdir etc var log and write a default etc/zope.conf? (Thanks to whoever came up with "bin/zopectl adduser", BTW, much appreciated!) Now the "using buildout" section of INSTALL.rst leaves the user to write one completely from scratch without any tool support or even a link to documentation, and I'd like to fix this in case I have to set up a Zope 2.x instance ever again ;-) Cheers! Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development