Re: Remove configuration files from content directory

Andreas Hartmann wrote:
> Hi all,
> 
> I would suggest to alter the directory structure
> so that publication-specific configuration files
> are not placed in the content directory. This has
> a low priority, but if you agree, it could be
> solved quite fast using global search.
> 
> Motivation:
> 
> - It is confusing to put them in the content
>   directory.
> - We would have a common location for all
>   configuration files.
> 
> My suggestion is to create a directory named
> 
>   config
> 
> inside the publication directory and move the
> files there.

+1


> 
> The question is how much effort this takes.
> 
> tasks.xconf
> - some Java files
> 
> lucene.xconf, crawler.xconf
> - crawl_and_index.xml build file
> - search XSP
> 
> publication.xconf
> - publisher and exporter classes
> - ?
> 
> I would implement all changes for the tasks.xconf
> file and maybe the lucene and crawler files.

I think there is no need for changes for lucene.xconf and crawler.xconf,
because these files are just specified as arguments for ant, so no 
reason to worry ;-)


> 
> Another question is how to distinguish between
> content / configuration / resources, e.g. regarding
> the scheduler jobs dump file (it seems to be similar
> to the search index - so is it a resource?).

Well, the scheduler jobs dump file (for persistency) is an
XML file and does change if one stops the server. Hence I would
leave it within the "content" directory (this file could also
be viewed from the admin area).

Michael



> 
> Andreas
> 
> 
> _______________________________________________
> WyonaCMS-dev mailing list
> [email protected]
> http://wyona.org/cgi-bin/mailman/listinfo/wyonacms-dev
>