directory layout and deployment best practice

Dear list,

I've been reading mailing list archives, the FAQ, the Wiki and the
manuals, but I haven't been able to find what I was looking for.

What is considered to be best practice with regards to the directory
layout and deployment of SkunkWeb applications?  For example, should I
just integrate my application code / components with the global
docroot?  What am I supposed to do with python modules and packages
required by my skunkweb components, i.e. where exactly should this go
(I obviously don't want this kind of library code hanging around in
the docroot)?  If these library modules go somewhere else, what's a
consistent way to adapt the sys.path in all my skunkweb components?

I think my main question is: how do I keep my own code and the
SkunkWeb installation directory separate?  I would prefer not to have
to copy my own modules to the pylibs directory for instance, as this
would complicate upgrades and the like.

I would appreciate any advice or information about what experienced
SkunkWebbers are doing.

Thanks,
Charl

-- 
charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/

c.p.botha ||at|| ewi.tudelft.nl - tu delft work-related email
cpbotha ||at|| cpbotha.net - everything else


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf