Michael Wechner schrieb:
> 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?
>
> yes
OK - would you mind explaining your usage scenario?
Maybe it is possible to find a different solution to meet
your requirements.
The only scenario that comes to my mind ATM is to distribute
the content over multiple partitions/disks, but this would
probably only be necessary if there are millions of documents.
And in this case it should IMO be a concern of the repository
service.
Another one could be to store the content in the publication
source directory, which would make it easier to put it into
the same SVN repo. But this could be managed by checking out
the content directory in another location as well.
>> 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.?
>
> I don't think so, because I think every publication should be
> self-contained.
The publication could still be self-contained:
/data
/pub1
/content
/access-control
/search-index
/...
/pub2
/content
/...
OTOH, I can imagine to have global data repositories, which could
simplify multi-site publishing. But this is certainly something
for 1.6 or later.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
