On Sun, 2006-02-12 at 20:30 +0200, Ilias Lazaridis wrote: > version: 0.93 > > I have multiple projects, each with a domain, served via tracd on a > apache server. > > - > > tracd -d -p 9999 /proj1.org/trac/proj1 /proj2.org/trac/proj2 > > Those projects become available as (using just the roadmap link for demo): > > proj1.org/proj1/roadmap > proj2.org/proj2/roadmap > > But I dislike the redundant parts > I don't think tracd has any options for how projects are represented. As far as I understand, it's really not meant to be particularly configurable -- it's more of a "quick, minimal setup".
If you can use Apache and mod_python instead of tracd, however, then you can put your Trac URLs wherever you like. See <http://projects.edgewall.com/trac/wiki/TracModPython> for example setup instructions, including virtual hosting. For the setup you described: proj1.org/trac/roadmap proj2.org/trac/roadmap You'd create two virtual hosts, a <Location "/trac"> section in each one, and set TracUriRoot to "/trac" on both of them (or leave it unset). If you'd prefer to have Trac take over the entire domain, set "TracUriRoot" to "/" and you'll have URLs like: proj1.org/roadmap proj2.org/roadmap I don't know if you can do the same thing by trac under CGI... TracPrettyUrls <http://projects.edgewall.com/trac/wiki/TracPrettyUrls> describes using mod_rewrite but there is no mention of overriding TracUriRoot. -- Rob _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
