Hi. > What is /proj/htdocs directory for, and is it documented anywhere?
See for example: http://trac.edgewall.org/wiki/TracStandalone#Servingstaticcontent > I use Javadoc, Doxygen, etc. in my projects. I can use e.g. commit hook to > automatically generate API docs -- static html pages. So far the only way > I found to link them to trac's project page is to place them outside of > /proj directory (and out of mod_python's reach). What would be the sense in having the static pages in reach of mod_python? Isn't Apache the instance that should have access to these static pages in order to serve them (that's one of the easiest and most basic tasks for it)? > Frankly, I am surprised this isn't in the FAQ: doesn't anyone document > their code? I guess it's not in the FAQ simply because it is none. Most users seem to realize the difference between the Trac environment and static content that is served on the same domain (but usually from a different directory). If you still want to have your static files in the htdocs/ subdirectory of the Trac environment, you should consult the documentation of your webserver and check how to change the document root of the corresponding (virtual) host. Just my 2 cents. Bye, Mike _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
