Re: Remove configuration files from content directory

> purpose (for web applications). If I understand the
> idea correctly, all files that replace / extend default
> Lenya files shall be put into the <pub-id>/lenya
> directory. Is this right?

yes

> We could expand the publication directory structure to
> 
> <pub-id>/bin
>          /content
>          /java
>          /lenya
>             /config
>             /WEB-INF/lib
>                     /logs
>          /resources
>          /xslt
> 

-1


> <pub-id>/bin
>          /config       (additional and overriding files)
       same structure in here as in content and xslt:
             /ac
             /authoring
             /publishing
             /rc
             ..

>          /content
>          /java         (only in source dir.)
>          /lib          (only in source dir.)

       or  /java/src
           /java/lib

     would be more logical. i was initially against 
     /java/src, but now that we have subdirs there lets
     put lib there too.

>          /logs         (only in install dir.)
>               /tasks   (task log history)
>          /lenya        (only override content or xslt)
                         and resources

>          /resources
>          /xslt

the question is what to do with stuff like 

content/ac which are arguably config files too. etc.

-gregor

-- 
Gregor J. Rothfuss   [email protected]  +41 1 272 9161
                     Wyona AG, Hardstrasse 219, CH-8005 Zurich
Open Source CMS      http://www.wyona.org http://www.wyona.com 

OSCOM 3 - Third Open Source Content Management Conference
May 28th - 30th 2003, Harvard University, Cambridge, MA, USA
http://www.oscom.org/Conferences/Cambridge/