This issue is address by the subscription system in TracForge (currently working for tickets and changesets, but not wiki pages). You create one central Trac that aggregates the data from several others, and then run any needed queries on that. For this specific case I would probably need to add something to transform the component field as the ticket is copied over, so it contains the prefix in the aggregate, but not in the source.
--Noah On Sep 28, 2006, at 10:08 AM, Jason Winnebeck wrote: > > Sorry for kind of jumping in but I've been listening to this and I > am a > little confused. How good is the current state for TracForge? > > We have multiple projects, one Trac for each SVN. One Trac contains a > ton of different projects inside of it, managed as components like > "Project A - Component". This was chosen because of the SVN set up. > But we also have 3 other Tracs. > > Really all I am looking for besides a way to do substring queries on > component field for tickets is a way to merge timelines, tickets, and > RSS from multiple Tracs. Right now I have responsibilities in > multiple > Trac environments so I have to run the same query on both. I have > thought even of making a tool to use the XML-RPC plugin (which I > haven't > tested) to do multi-Trac queries. > > Is TracForge to that level yet? As for multi-project management I > already have that 100% handled because when I made the projects I > wrote > a tool to manage global permissions and configuration options across > multiple environments so that part is handled. > > Jason > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > On Behalf Of Noah Kantrowitz > Sent: Thursday, September 28, 2006 9:55 AM > To: [email protected] > Subject: [Trac] Re: RFC - about a mini tracForge > > > > On Sep 28, 2006, at 9:36 AM, zwetan wrote: > >> >> >> >>> Things like getting a unified look and feel would get annoying very >>> quickly. I'm not sure what you think cannot be done from within >>> Trac, >>> because I haven't yet found anything. TracForge only needs to >>> provide >>> the project (read: env) management tools for this, as there are a >>> rich set of plugins for configuring each env, and I see no reason to >>> duplicate this. >>> >> >> well for unified look >> I will just modify 1 template in the main Trac >> to add a navbar on the top that's all nothing more >> >> and after the goal is that each user being able >> to edit their own trac.ini to configure their logo, etc... >> but as it would not be secure to let them access >> directly the trac.ini file >> hence a web admin is needed to do that > > See also Alec's wonderful IniAdmin plugin. > >> >> the goal is to be able to serve ~100 Trac which could have >> all different settings per user need >> - not the same user rights >> - not the same SVN hooks >> - not the same backup process >> etc. > > Considering that Trac has no inherent scaling issues (aside from > SQLite, which is unavoidable) that I know of, I don't see why this > needs to be out-of-band. TracForge already provides for both global > permissions/roles, and local ones. > >> >> sure trac can handle user rights from the admin >> but from Trac you can not define SVN hooks, or you need to make a >> plugin >> from Trac you can not run backup of the Trac db and the SVN repo, >> another Trac plugin > > Of course it can. Just run a bunch of select * queries, and build out > a new schema design from that, then send the rendered schema (using > the DatabaseManager's to_sql() results) and the rendered inserts back > to the browser. For Subversion you would probably need to call > svnadmin dump and capture the output (trivial using the subprocess > module). > >> >> all those kind of automation process can be done from shell script, >> or best from a web admin running the shell script >> >> but perharps I see all that too much from a host admin point of view >> >> zwetan >> >> >>> > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
