Michael Renzmann wrote: > Hi. > >> What is /proj/htdocs directory for, and is it documented anywhere? > > See for example: > http://trac.edgewall.org/wiki/TracStandalone#Servingstaticcontent
I see. So htdocs is there for tracd only. > 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)? Well, my first instinct was to keep all project webpages in one place, under /proj, and /proj/htdocs looks like the place for static content. >> 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). So did I, after wasting an hour playing with apache settings. It'd save me some time if the docs spelled it out somewhere outside of "Tracd" section (which I didn't read because I have no intention of running tracd). Thanks Dima _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
