Comments on: Trac & Git

By: Jeroen Knoops

Jeroen Knoops — Thu, 16 Jul 2009 16:13:15 +0000

I had this problem on Debian (Lenny) as well.
I also had to manually build it and added

[components]
gitplugin.* = enabled
tracext.git.* = enabled

and had to give www-data write access to the repositories.

By: tdwebste

tdwebste — Mon, 02 Feb 2009 14:59:12 +0000

Using trac, git plugin, gitosis is quite easy. The problem is it only supports one repository.

I use debian, which correctly installs gitosis
read the example.conf

but debian’s trac git plugin was broken, build your own

trac
/conf/trac.ini
[trac]
repository_dir = /srv/gitosis/repositories/genist.git
repository_type = git

[git]
cached_repository = true
shortrev_len = 7
persistent_cache = true
git_bin = /usr/bin/git

ping if you need help

By: Amol Hatwar

Amol Hatwar — Fri, 23 Jan 2009 02:21:55 +0000

Just getting trac and git to work together has caused nightmares for my team, the development version especially. I am surprised to hear praises.

On the other hand, it will be great if you could publish the ingredients of your trac+git magic sauce. (My team also hates SVN).

By: SIlas Sewell

SIlas Sewell — Thu, 25 Dec 2008 05:37:19 +0000

Lighttpd now uses Redmine.

http://redmine.lighttpd.net/

By: yohoho

yohoho — Thu, 03 Apr 2008 19:23:25 +0000

About having to check multiple RSS feeds, why not just setup a planet that compiles them for you and then check that planet?

trac has really flexible authentication: it relies on the web server’s authentication policies.
So if you’ve configured apache reasonably, you should be able to have one login that would get you at all the different trac instances.

For interlinking between trac instances, there’s a simple InterTrac
wiki link syntax

Integration isn’t so great, its true (for example how do you pull ticket reporting pages together so you can see a list of your highest-priority tickets, regardless of project)

By: Anonymous

Anonymous — Wed, 26 Mar 2008 12:39:45 +0000

I’m another happy drproject converted (from trac), and considering a Mercurial backend

By: The Changelog

The Changelog — Mon, 03 Mar 2008 21:16:02 +0000

A few days ago, I discussed Trac and Redmine. Redmine is a project management tool, similar to Trac, with built-in download tools, bug tracking, etc.

Redmine has a lot of nice features. Chief among them is better integration between multiple projects

By: John Goerzen

John Goerzen — Sat, 01 Mar 2008 16:52:24 +0000

Well, that gets unwieldy for a few reasons. One is that each project has its own repo, which Trac doesn’t necessarily grok. Another is that the file downloads area would be a mess. Finally, the wiki pages could clash, etc.

Also it would not be possible to authorize someone to one project but not another.

By: Vespe Savikko

Vespe Savikko — Sat, 01 Mar 2008 14:09:14 +0000

Have you considered just incorporating all your projects into one Trac project? Then the former projects could be just components under the big umbrella project. Naturally, there could be some showstoppers that I am not aware of.

By: thekaos

thekaos — Sat, 01 Mar 2008 06:04:25 +0000

Ok, you seen to have small repositories. My trac is over the full gcc git repository, and is frankly unusable, we had to disable trac’s browser.

However having a small repository does just makes the load manageable, but your apache will use lots of cpu compared to svn.

GitPlugin people are well aware of the issue, which is a design defect, but it will take a lot to be fixed.