On Fri, Mar 12, 2010 at 11:53 AM, Cooke, Mark <[email protected]> wrote: > FYI: mod_python or mod_wsgi is not directly relevant to this problem.
That was mainly to indicate which documentation I was reading, in this case: http://trac.edgewall.org/wiki/TracModPython#Settingupmultipleprojects > In what way is this not clear? What are you trying to achieve? Each > trac environment (currently) links to only one repository and that > should be on the same machine as the trac environment (and accessible to > the apache user too). Different trac environments usually link to > different repos but they all need to be local file paths, you cannot use > a network path (e.g. http:// of svn:// style path)... > > The 'path to repository' is the file path to the repo directory (which > will have 'conf', 'db', hooks', 'locks' etc for fsfs). What this is > depends on your local setup and platform, *nix will be a path from root > whilst windoze needs the drive & path (e.g. d:\svn\repo_name). > > If you leave it blank, you can edit the [trac] section of your > repo-dir/conf/trac.ini to add the path in: > [trac] > repository_dir = d:\svn\repo_name > > ...after saving this you would need to run (for svn repos): > >> trac-admin <path-to-env> resync > > ...and possibly restart your trac server (not sure but it shouldn't do > any harm). I was not sure this was the 'way to go'. I created a trac installation per svn repository. This seems to work ok. We are loosing the ability to report a bug across two projects however. We'll see as we go if this is important or not. Thanks anyway for your clarification, -- Mathieu -- 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.
