On Mar 2, 2006, at 2:56 AM, Martin Tomes wrote:
Having failed to persuade this community that putting multiple project
support into Trac would be a good idea I am back here again to pursue
the apparently more acceptable idea of having a separate web
application
which coordinates and views multiple Trac instances. I have trawled
through the responses to my previous posts and have come up with this:
http://projects.edgewall.com/trac/wiki/TracMultipleProjects/MultiTrac
It is currently a list of requirements which I haven't even sorted into
order of importance. We have resource to implement some of this coming
available in two to three weeks and I would appreciate feedback on
these
requirements.
I've implemented a few pieces of that. I have a page which provides
links to all projects, a page which displays all tickets assigned to
the logged-in user, and a form for creating a repository and the
corresponding Trac project. All of that was pretty trivial to write.
The main problem I ran into is that querying all of the Trac project
databases can be slow. Displaying all of my tickets in 23 projects
takes about half a second on a decent server. That's not going to be a
problem for most people, but you wouldn't want to do it on the scale of
Sourceforge.
I can look into getting my tools released if you're interested, but it
would probably be less work to rewrite them.
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
