John, Thanks for taking the time to write these very complete answers...
John Hampton <[EMAIL PROTECTED]> writes: > David Abrahams wrote: >> Has anyone thought about this? > > Lots of people have > >> Is there a solution out there already? > > Kind of. If you use trunk, and PostgreSQL, then you can put each > "client" in a separate PostgreSQL schema, instead of database. This > will make it easier to write a custom report, as querying across > schemas is possible. And if I have existing Tracs in databases, can I move them into PostgreSQL schemas? > The other option is to use the security sandbox [1][2][3]. It will > give you finer grained permissions, though I think it is largely > untested beyond alect the developer. It looks really attractive. There are only two apparent problems: 1. Migrating existing multiple Tracs into a single one doesn't sound trivial. 2. it seems like it would be hard to control Wiki access nicely. I don't really want to manually exert control on a page-by-page basis; in fact, what I get now with separate Tracs is almost ideal where the Wikis are concerned: there's a big playground for each client where they can create and view pages at whim. I suppose one might fake it by allowing a client to create/view pages with a particular prefix or something... > Additionally, there have been various discussions about multiple > project support in a single environment, etc. All that has really > been decided is that it's a >1.0 feature. Gotcha. Thanks again. -- Dave Abrahams Boost Consulting www.boost-consulting.com _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
