2009/10/7 Olemis Lang <[email protected]> > > > > > > ooo... does it inherit users and preferences across projects? > > > > Shouldn't do that unless you use centralized auth (e.g. LDAP) and > inherit config options (e.g. server, port, ...) or use (basic | digest > | ...) and inherit options for httpauth file, so that credentials be > retrieved from the same place. The only thing that's inherited is > config options, but if this means that all projects will use the same > auth options then all prjs will behave the same way ;o) >
Ah that's a shame... I have script that basically allows me to set up projects that does exactly what Remi described, but with Trac 0.11stable. We use apache as the front end and hook into subversion, so we have a common htpasswd file for apache, trac and svn. Works great. Only "problem" I have is that each project has its own unique database, so every time I set up a project and give a user permissions to access that project, they also have to go in and set their email address and real name in the preference. I keep meaning to go through http://trac.edgewall.org/wiki/TracMultipleProjects/MultipleEnvironmentsSingleDatabase, but the caveats and time keep stopping me. Thought maybe 0.12x was going to magically let me share users and preference and save me the hassle. ;-D Ah well Never mind... I'll just have to get a minion to look at it for me ;-) Stephen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
