Multiple Projects using Multiple Trac Environments

This is the traditional way of handling multiple projects with Trac: create a new environment for tracking a given software project.

That way, each project is managed independantly from the others. This can be achieved using mod_python and tracd. Further technical documentation about the setup can be found in TracMultipleProjects.

This page is for discussing open points related to using multiple environments for managing multiple projects, and for contrasting this approach to an alternative approach described in TracMultipleProjects/SingleEnvironment.

One or Multiple Repositories?

It is straightforward to manage multiple repositories using this approach: as each environment is based on a given (Subversion) repository, simply create an environment for each repository, as required.

However, there are two common situations that are quite common and are currently not well addressed:

1. the different repositories are within the same company or team (e.g. one repository for some legacy application, one for new applications, one for the common components, …) and there is a need to have some kind of integration between the projects
2. there's only one repository actually, containing many projects

The first concern was expressed in #234. A proposed solution was to introduce the InterTrac extension for TracLinks.

The second concern was first expressed in #586, and has been reiterated several times since (#1025, #1059, #1398). Since [1413] (the new versioncontrol layer), there is actually support for working on a subset of a repository, but this will only work if the project is fully self-contained within the given URL.

Aggregate Reports

Since each project has its own database, it's difficult to get an overview of activity for all (or a set of) projects.

One option to help with this is TracMultipleProjects/MultipleEnvironmentsSingleDatabase