At my company we have several subversion repositories, each with its own trac project. One of the subversion repositories is quite active and now has about a dozen subprojects in it, all associated with the same overall software product. Its trac project is quite busy and a couple of groups would like to have their own trac instance, tied to this same subversion repository. They could then keep the trac wiki and tickets on their trac instance focused on a particular subproject. If there were the original trac instance plus two additional ones, each trac would see the same subversion repository (which is a 'read-only' operation), but each trac would have its own, disjoint set of tickets and wikis. It's the 'disjointed-ness' we are seeking. Any there any unseen problems with this?
For the current trac instance associated with this repository, we use SQLite for our trac database, with the database located in the db directory under that that trac project. Bill --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
