Andreas Hartmann wrote:
Hi Lenya devs,
I wonder if it is really appropriate to configure the content
directory per publication and not globally.
Does anyone need separate content directories for publications?
i don't, and i'm all for simplifying stuff.
"convention over configuration" was the big buzzword at the cocoon gt,
and i found it very convincing. lenya has got many configurable things
that nobody really seems to use, which mean they tend to break when you
use non-default settings. the less of those we keep, the less we have to
maintain.
IMO the major purpose is to separate data from the web application
for deployment and backup reasons.
Wouldn't it be easier to configure a global "data directory"
which is used for content, user data, search index etc.? This
could be overridden by configuring the single components
(e.g. the SourceNodeFactory or the Lucene index).
+1
--
jörn nettingsmeier
home://germany/45128 essen/lortzingstr. 11/
http://spunk.dnsalias.org
phone://+49/201/491621
if you are a free (as in "free speech") software developer
and you happen to be travelling near my home, drop me a line
and come round for a free (as in "free beer") beer. :-D
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
