On Dec 6, 4:02 am, Danny <[EMAIL PROTECTED]> wrote: > I apologize, I believe I misspoke in my previous post. I have set > the trac.ini setting for 'htdocs_location' and the respective symlink; > it works properly but it only applies to /common/ files, the static > files from the trac distribution itself. I'd like to know if there is > configuration available for a similiar setting for the /site/ specific > htdocs folder, if not I'd be more than happy to inquire on the > development list and perhaps poke around myself. > > The purpose being that /site/ specific static files can also be served > by Apache rather than by the trac cgi itself without having to resort > to Alias-es. Since there is a setting for common files, I figured > there might be a way of doing the same for the site files.
That htdocs_location exists is possibly more as a convenience so that one can configure the URLs so that they don't overlap with the Trac URL namespace. In practice this probably isn't required. Through appropriate ordering of directives in Apache it should be possible to map what is a subset of URLs in Trac namespace to actual physical files. In other words, you shouldn't need a feature in Trac to do it. To do this though would most likely require you have access to main Apache configuration. If you only have access to .htaccess file, then may be harder or not possible. I'm not really a Trac user so you'll need to help me out here. First off, ignoring htdocs_location, what URL within your Trac instance would these static files normally reside at? Give me that and what Apache configuration you are using to get Trac to work for you and the URL for the top of the Trac instance and I'll give some suggestions. Graham > On Dec 4, 5:19 pm, Graham Dumpleton <[EMAIL PROTECTED]> > wrote: > > > 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 -~----------~----~----~----~------~----~------~--~---
