[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: issue tracking, code diff/review

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Tue, 22 Mar 2011 11:20:12 -0400

On Tue, Mar 22, 2011 at 9:22 AM, Cooke, Mark <mark.cooke_at_siemens.com> wrote:
>> >> -----Original Message-----
>> >> From: bruce [mailto:badouglas_at_gmail.com]
>> >> Sent: 22 March 2011 05:34
>> >> To: users_at_subversion.apache.org
>> >> Subject: issue tracking, code diff/review
>> >>
>> >> Hi.
>> >>
>> >> I've got a basic workflow app that allows users to manage software
>> >> apps, for different roles. For the "review" role, I'm trying to find
>> >> a simple issue tracking app/code diff/review app that I can modify,
>> >> to hook into what I'm creating. I've started looking into
>> >> mantis/indefero, etc...
>> >>
>> >> Something simple/free would be useful!! I know I'm going to have to
>> >> merge login/user tbls, and probably other tbls regardless of what I
>> >> choose.
>> >>
>> >> Any thoughts/comments would be appreciated..
>> >>
>> >> Thanks...
>> >>
>> > On Tue, Mar 22, 2011 at 5:45 AM, Cooke, Mark wrote:
>> > Trac: http://trac.edgewall.org/
>> >
>> > ...tickets, configurable workflow, good support for subversion e.g.
>> > can (re)view changesets from inside Trac.  Trac is extensible (check
>> > out http://trac-hacks.org/ for lots of samples) and open source Python.
>>
>> -----Original Message-----
>> From: Nico Kadel-Garcia [mailto:nkadel_at_gmail.com]
>> Sent: 22 March 2011 12:49
>> Subject: Re: issue tracking, code diff/review
>>
>> Trac is *very* powerful and flexible. It's also a bit awkward to set
>> up with good permissions to allow the daemon that runs the web server
>> (typically as the "apache" user) to have write access to your back end
>> subversion, and to propagate any subtle permissions to backups of the
>> Subversion environment. I had considerable difficulty getting it to
>> work with the Apache "suexec" capability, but eventually succeeded.
>>
> Curious, why would Trac need write access to the subversion backend?
>
> Mine is configured on Windoze, so I guess I have fewer options to configure although I have tried to tie it down sensibly.  I had more problems learning how to setup apache (and am now having the same but different issues setting it up on an Ubuntu box at home).

Windows is a Different World(tm). I was working in Linux. The client
wanted a personally instlallable, manageable, replicatable, Trac
service. I wanted them to be able to do so safely and securely, so
that the normal Apache services of this and other tools couldn't step
on their dedicated Trac environment. This led me to suexec, which I've
dealt with before and used to work quite well with Trac, but the whole
Trac deployment architecture changed with version 0.12, and the RPM
contents changed significantly to go with it, so it took some
re-engineering.

Basically, I had to replicate the old deployment technique of setting
up a full Trac repository, with its own CGI script, to get the
per-Trac repository control I wanted. Unfortunately, I left my notes
at that contract. I could ask them for a copy, if it would be useful
to folks here.
Received on 2011-03-22 16:20:44 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.