Dear Experts,
I have a single svn repo with multiple projects as top-level
directories within it.
Currently I have a single trac instance that points to this repo.
(When I installed it, I guessed that I would be able to define the
projects within trac, but then I realised that trac only has
"components", not "projects", at that level.) Until now I've been
using this trac instance for just one of the projects.
Now I want to support a second project. Hopefully I can do something
like this:
- Change the Apache config to use TracEnvParentDir instead of TracEnv.
- Create a new trac environment for the second project.
- Leave the repository_dir in both trac environments pointing to the
same repo.
So both trac instances will see the root of the repo in the source
viewer; that doesn't bother me, but if there is some way to make it
start one level down I would like to hear about it. But, is is
fundamentally OK for both trac environments to point to the same svn
repo? Will they get confused and trip over each other?
Also, is it safe to go from TracEnv to TracEnvParentDir with an
existing project?
(In other situations I would be tempted to just "try it and see", but I
really don't want to do something that will mess up my existing
project's trac data.)
FYI I'm using the Debian package of trac, version 0.11.1-2.1, currently
using mod_python.
Thanks for any advice.
Regards, Phil.
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en.
