Hi Lenya devs,
at the moment, it's pretty much up to the user to configure the location
of the publication data (content, search index, access control data, …).
This works well for directly referenced data, but causes problems with
fallback-endabled resources, like usecase-policies.xml. Apart from that,
the configuration options are scattered across several files.
Following the convention-over-configuration principle, I could imagine
that it would be useful to have a fallback-endabled data directory with
a configurable location.
One option is to configure this globally for all publications, e.g. in
local.build.properties:
data.dir=/home/john/lenya/data
The directory structure could look like this:
$DATA_DIR
/pub1
/content
/access-control
/passwd
/policies
/usecase-policies.xml
/search-index
/…
/pub2
/…
Resources in the data directory could be addressed using the fallback
protocols, e.g.:
aggregate-fallback://data/access-control/usecase-policies.xml
I'm not quite sure yet if this makes sense and if it could be
implemented without complications. WDYT about the general idea?
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
