On 6/22/08, Wolfgang Jeltsch <[EMAIL PROTECTED]> wrote:
> Am Sonntag, 22. Juni 2008 20:04 schrieb Andreas Hartmann:
> > Wolfgang Jeltsch schrieb:
> > > My current solution is to have a source tree with all files I want to
> > > change manually (like publication.xml) and have symbolic links in the
> > > publication directory, pointing to the files/directories in the source
> > > tree.
> >
> > BTW, another approach is putting as many files as possible in modules
> > (which I'd recommend for several reasons) and set modules.copy=false in
> > local.build.properties.
>
> What can be put into a module?
> * publication.xml?
> * XSLT files?
> * CSS files?
> * I18n files?
> * Images to be automatically inserted into each page?
>
> Best wishes,
> Wolfgang
Thank you for an idea. (This coud be theoretical since I am not
familiar with Lenya 2.x, but the thoughts do apply to my demo.) The
last four items should be in Modules. publication.xml needs to define
the Publication:
- content: the location and type of repository.
- code: which Modules to include and where are any Publication-specific Modules.
- security: the type and connection information for a directory or the
location of Lenya's XML files (whether shared or
Publication-specific.)
The new idea is that a file named publication.xml does not need to be
in a directory named with the publication-id. The information could
be placed in a file named {publication-id}.xml in the pubs directory.
A publication directory is not needed if the content-code-security
data can be stored outside the Lenya directory. Lenya can be upgraded
or reinstalled without affecting the Publications (assuming everything
in the Publication is compatible with the different versions of
Lenya.)
Thank you,
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
