Changes between Version 35 and Version 36 of TracMultipleProjects/ComprehensiveSolution
- Timestamp:
- Jul 2, 2007, 2:12:34 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracMultipleProjects/ComprehensiveSolution
v35 v36 58 58 59 59 60 == What's Wrong With Sharing a Single Trac? == 60 == Why Some Other Approaches Don't Quite Work (Yet) == 61 62 As #130 shows, this has been an area of intense interest, and several alternative techniques have been tried. To date, none of them meet my basic requirements. I explain why below. 63 64 === Sharing a Single Trac === 61 65 62 66 There's been some work on [TracMultipleProjects/SingleEnvironment managing multiple projects within a single Trac instance], but Trac can't yet give my customers the privacy they need in a shared environment. Sometimes we're working on proprietary software that ''must'' be kept private, but even when we're working on open source, customers generally feel uncomfortable when all their issues are automatically exposed to the world. … … 69 73 Naturally, the same kinds of issues apply to other resources such as Milestones. Upon creation by a customer, they need to be private to that customer and (some subset of) my people. When ''I'' create these resources there needs to be an ''easy'' way to make them private to a particular customer's company. And I'm sure that other people will have vastly different "permission workflow" requirements than I do, so the system probably needs to be more flexible than what I've described. 70 74 71 == What's Wrong With Previous Attempts to Leverage PostGreSQL Schemas? == 75 I do think this approach has a future, I just don't know how close it is. 76 77 === Previous Attempts to Leverage PostGreSQL Schemas === 72 78 73 79 TracMultipleProjects/MultipleEnvironmentsSingleDatabase describes two approaches to using PostGreSQL schemas for doing multi-project reports: … … 77 83 * The [TracMultipleProjects/MultipleEnvironmentsSingleDatabase#PossibleAlternative second (alternative) approach] is much simpler, but it also has a fatal flaw: although you can get a report, clicking any of the tickets still takes you to the ticket with the same ID as the ticket you clicked, but in the current project. 78 84 79 == What's Wrong With !TracForge Ticket Subscriptions?==85 === !TracForge Ticket Subscriptions === 80 86 81 87 [trachacks:TracForgePlugin TracForge] contains a feature called "subscriptions" that replicates data from one trac instance to another. One could try to use that to make all those tickets available in a master project where they can be queried. However,
