Improve tracd's handling of multiple projects

[mikec@…]

Currently, tracd handles multiple projects by accepting multiple environment names on the command line. This has a restriction, in that the last node of the path to each environment must be distinct; a command line like
tracd \\svr\projectA\Trac \\svr\projectB\Trac
fails to recognize the second environment because both directories are named "Trac".

This enhancement requests two things: 1) Remove the restriction: be able to identify different environments which reside in identically-named directories.

2) Rather than requiring the individual environments to be explicitly named on the command line, accept an environment-list file that can contain the various directory names (please don't require they all be on a single line).

[Christian Boos]

Well, this is certainly possible to do, but it sounds a lot of trouble to add this additional level of indirection between the Trac instance name and the Trac instance environment, especially as it seems that the vast majority of the other people installing Trac never felt such a need…

[mikec@…]

Your "additional level of indirection" appears to address item (2). Are you also rejecting item (1)? Because the restriction that you have in place is arbitrary and annoying; why should I need a unique directory name for each project when it already has a unique path?

As for "a lot of trouble" to implement (2), I don't see it. I understand your group doesn't have many resources, but this doesn't appear to me to be that difficult. It is, however, difficult for someone to create a plugin or other enhancement to make this happen — this kind of change needs to be implemented at the core of the product.

We are a consulting firm that frequently adds and removes projects from the overall environment. Currently, we have to go into the registry (in Windows) to change the arguments to the tracd service — SrvAny starting Python with an argument string that, with a single project, is over 100 chars long. With this change, we could simply open the project-list file and make the edits there in a straightforward way; with each project on a single line, editing would be simpler and less prone to errors.