Trac allows you to put in a path inside a repository as the repo path. something like /path/to/repo/proj1
This will set that trac installation for that project. Assuming you have your subversion tree organized well, this should work for you. We've just began using this, but have only seen one issue so far in that you'll have to write a custom post-commit hook if you want to use one, that will update the proper trac install based on the path to the project. Russ Myron A. Semack wrote: > Hello everyone, > > I am interested in using Trac in our organization. I've been looking for a > lightweight SCM type system, and Trac seems to be close to what we need. > However, I'm not sure if it is a good fit for us. > > Here's a little background: > > We currently use Subversion as our source control system. We use it to keep > track of both our software projects and hardware designs (Board schematics, > PCB layouts, etc). Because we share a lot of files between projects, we > have one big repository for all of projects. Our repository is pretty big > (11.5GB, close to 14000 revisions). We group the projects together into > directories and subirectories in the repository. > > In terms of code size, most our projects a pretty small. Most of them are > one-man projects. However, we sell A LOT of different board-level products. > There are several hundred projects in our SVN repository. > > We also have an issue tracker (FogBugz). It works well, but it can > sometimes be unwieldy for the large number of projects we have. > > I've been looking for an SCM tool to help, but a lot of the things I've seen > are overkill for us. Our projects are too small to benefit from heavyweight > processes and policies. It seems like a lot of SCM tools seem to be geared > for lots of developers working on a single large project, which isn't us. > We have lots of developers working in parallel on (somewhat) independent > products. > > Anyhow, Trac looks good, but I have some doubts about it because multiple > project support seems to be lacking. According to the Roadmap page, it it > listed alongside "alien technology". Based on that, I would guess it is > pretty far off :-) > > Whatever we use for SCM, it needs to support multiple independent projects > in a single repository. The "one repository per project" model does not > work very well because we share code between projects. It also adds > management overhead (Apache configuration, having several repository to back > up, several sets of hook scripts, etc). With several hundred projects, the > per-repository management overhead gets pretty rough. > > It also needs to have an easy-to-use system for creating new projects (e.g. > Fill out a form on a web page, click "create"). Anything that requires > command-line access on the server, or editing configuration files is > impractical. Especially with how many projects we have to manage! > > So, does it sound like Trac will work for us? Does it allow for multple > projects in one repository? Does it have a web interface for > creating/managing projects? > > Any insight you can offer would be very much appreciated! > > > > Sincerely, > > Myron A. Semack > > Director Software Engineering > > > > RTD Embedded Technologies, Inc. > > 103 Innovation Blvd. > > State College, PA 16803 > > Phone: 814-234-8087 > > Fax: 814-234-5218 > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
