John Hampton wrote:
> <Location /projects>
> SetHandler mod_python
> PythonHandler trac.ModPythonHandler
> PythonOption TracUriRoot /projects
> PythonOption TracEnvParentDir "/var/projects/trac"
> </Location>
> <LocationMatch "^/projects/[[:graph:]]+/login">
> AuthType Basic
> AuthName "Project Trac sites"
> AuthUserFile /var/projects/conf/projectusers
> Require valid-user
> </LocationMatch>
>
> Now, with the proposal, I think I can rewrite this config as:
>
> Request "/projects/.+/login" {
> Auth {...}
> }
>
> Request "/projects/.+/" {
> Handler cgi {
> Scriptalias /usr/share/trac/cgi-bin/trac.cgi
> Env TRAC_ENV_PARENT_DIR "/var/projects/trac"
> }
>
> Now, I could be completely off base and this won't work even under
> the new proposal. However, that is kind of what I'm after. I'm
> looking at replacing my existing apache installation and rely
> heavily on trac. It's possible to host multiple trac sites by simply
> adjusting the configuration for each one, but I'm sure you can see
> that isn't a desirable option for more than 2 or so sites.
Yeah, that configuration should work with the new Request entry
support. I'm quite confident it is a good thing to have. The only
thing left is to make a decision on how to manage the precedences
between directories, extensions and requests.
BTW, it seems like the configuration scheme we are proposing is far
more readable than the Apache one. Grand. :-)
--
Greetings, alo.
_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
