On Nov 4, 2:17 pm, Rob <[EMAIL PROTECTED]> wrote: > I have been using assembla for code and project management, and since > they've dumped their free model and I do work for non profits, that's > a dead end. I'm investigating other options. > > It seems that Trac is a reasonable alternative. I haven installed it > yet, and have some questions, particularly in regards to multiple > projects. I've looked through the demo, and everything seems to > assume that it is all about one project. How does one go about > starting a new project in Trac? Do I need a separate Trac > installation for each project? > > If anyone has experience with Assembla and can make other direct > comparisons - for better or worse - I'd really appreciate it. > > Thanks.
Hi We use Multi-project setup here as well, so I thought I would comment. Our projects are related, but each has a separate source repository, so the natural fit was mutliproject setup for trac. We use apache, with mod_python: http://trac.edgewall.org/wiki/TracModPython all our projects are in the parent directory, so going to ourserver.domain:port lists all the projects using the projects automatically if set up as listed on the above linked page. Here is the exact link into the page: http://trac.edgewall.org/wiki/TracModPython#Settingupmultipleprojects I am considering moving to mod_wsgi, but I am not much of an admin, it's not my day job, so when I have time to learn something... note, sharing a single subversion repository for multiple project can be done, but is not as easy as what I am discussing here. anyway. creating a new project is a matter of trac-admin /parent/dir/ location/newproject initenv answer the questions, and restart the apache server. setting up authentication in apache can be a bit tedious, but once it is done, it applies to all the projects. then, some things that become helpful: learn how to set up interTrac links if your projects are related install the mutli-project search plugin (very handy) learn to use the "inherit" feature of trac for common configuration settings. virtual servers in apache make it even nicer, wish I had that option here.... the post-commit hook scripts for subversion are worth their weight in gold, maybe even platinum. since time tracking seems to be of interest, you might want to look at the TimingAndEstimation plugin, or the TracHours plugin(s) We like this setup, I used the PrivateWiki plugin and created private wiki pages for each developer. They use that to keep developer notes for each project(very handy to link to a ticket, and/or a code branch/ revision in the note) now that we are multi-tasking a lot, we created a top level "software stuff" type project, and moved the private wiki pages to that "project". that is also the repository we put tools and junk in, links to tips, and a general calendar of software team things. That is also where I create "task" tickets to communicate things to be done this week, etc. (work on project X, tickets 1,4,5; put in vacation requests by..., team meeting friday..blah blah) In other words, out of the box, it will work for you with the linked configuration and some apache-fu. add a little cusomization via plugins and usage model, and it's even better. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
