Git and Trac (or similar)

Question

In the past I have really enjoyed using Trac with subversion repositories hosted on some of my own servers. The integrated ticketing and online code browsing is very conven

Answer 1

We use Trac and both of the two Git plugins -- the GitPlugin as well as the GitWebPlugin. See, we actually have three repositories (long story) and Trac is still limited to a single-repository. So, I wrote my own plugin that defines wiki syntax (Macros actually) for referencing a repository, branch or commit and these link to the GitWebPlugin links. I was also able to write some git hook scripts so that we can reference, close or modify Trac tickets in commit messages -- it's a modified version of the SVN commit hook that comes with Trac.

The main problem with the GitPlugin is that it's slow due to the lack of "libgit" library. It's not bad for small-medium sized projects but large projects are a pain. If you really need a speedy web interface you should really check out Cgit. Cgit makes it's own libgit so it's tied to a particular version of Git.

The truth, however, is that web based views of Git are not that useful except when you want to send someone a link (like in email or IRC). Because with Git you have the full repository in every clone you're much better off using tools like gitk or even plain ol' git log. The queries and grepping capabilities are really amazing and (obviously) fast. I find that Cgit and GitWeb are really only useful for sending links to commits and that's pretty rare.