Hi! Rob wrote: <snip> > Do I need a separate Trac > installation for each project?
we use Trac for multiple projects in two different ways, for two different reasons. There are of course other ways of doing it, this is just what we do: 1. Multiple trac environments. ie. /var/lib/trac/proj1 /var/lib/trac/proj2. We use this method because we give specific access to the different environments to different customers who want to trac a project post release. Each environment shares the password file, but has completely different sets of tickets. Some are read-only, some they can add tickets to. 2. One trac environment, add a custom field. ie. only one /var/lib/trac/proj but I've edited [ticket-custom] to add a select box for listing the different projects. I've also edited the reports to tailor them for the extra field. We use this one internally as a bit of a task and defect tracker, so we can see individual's hours acrross multiple projects and tasks. > If anyone has experience with Assembla and can make other direct > comparisons - for better or worse - I'd really appreciate it. Sorry, never used it. HTH though! -- Iain Buchanan <iain at pcorp dot com dot au> Chris Griffin: It'll be a good chance to get away from the evil monkey that lives in my closet. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
begin:vcard fn:Iain Buchanan n:Buchanan;Iain email;internet:[EMAIL PROTECTED] tel;work:+61 (0)8 8947 0933 x-mozilla-html:FALSE version:2.1 end:vcard
