On Dec 5, 2:40 am, Danny <[EMAIL PROTECTED]> wrote: > Heh, you are right Graham, there is mention of serving project > specific files through apache, it just didn't 'click'. However, > although that information is somewhat useful, unforunately at my site > I don't have access to the apache Alias directive. I'm wondering if > there is an option, or a way of configuring it in trac.ini in the same > style that the 'htdocs_location' functions. Essentially creating a > symlink to the common htdocs, and simply setting the trac.ini to read > that, thereby not requiring the use of the apache directives.
You probably just need to set htdoc_location to URL which maps into your own personal web space where you can place files and/or directories of files. You probably will not be able to use a symlink as following symlinks is often disabled in Apache. Thus, you would need to copy the Trac htdocs directory into your own personal web space. Can't comment further as you don't go into how your Apache is setup as to allow you currently serve CGI scripts or your own personal static pages. Graham > -- > Danny > > On Dec 3, 4:54 pm, Graham Dumpleton <[EMAIL PROTECTED]> > wrote: > > > On Dec 4, 6:31 am, Danny <[EMAIL PROTECTED]> wrote: > > > > I'd like to know if its possible to map the static resources from > > > Trac's site and common paths to different locations using apache and/ > > > or trac.ini. > > > > I have read through and implented the suggestions in (http:// > > > trac.edgewall.org/wiki/TracCgi#MappingStaticResources) for mapping the > > > static *common* resources, but there doesn't appear to be any > > > indication or suggestions for mapping static site resources > > > specifically the $TRAC_ENV/htdocs directory. > > > Is there support for this in trac? > > > If so, where? If not, should I cross post to the dev mailing list? > > > Huh, isn't that what the section starting with 'Similarly, if you have > > static resources in a projects htdocs directory, you can configure > > apache to serve those resources' is explaining, or am I missing > > something? > > > Anyway, thanks for bringing this up, as the same techniques as > > described for CGI scripts carry over to mod_wsgi. I'll have to update > > mod_wsgi documentation to highlight this, as will help to lessen the > > work Trac has to do in that setting as well. :-) > > > > This question actually comes up again in the attachments, but I can > > > see the issue there with respect to needing the trac.cgi to authorize > > > the access to the attachments, in our particular enviroment it isn't a > > > big deal, authorization is handled by apache you are either in or your > > > out :). > > > > Any suggestions/thoughts would be greatly appreciated, thanks! > > > Don't know about attachments, but I also will be interested in the > > response. > > > Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
