Opened 19 years ago
Last modified 18 years ago
#1051 closed enhancement
Trac needs a central config file — at Initial Version
Reported by: | Manuzhai | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | high | Milestone: | 0.9 |
Component: | web frontend/mod_python | Version: | 0.8 |
Severity: | normal | Keywords: | |
Cc: | manuzhai@…, trac.tickets@…, dserodio@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I was just trying to trick the mod_python handler into displaying a prettier page where you can choose from different projects, and while I got it done in the end, it was not a very pretty solution. This was mainly due to the fact that only the env knows about things like template locations, htdocs_location, and other stuff.
To make it easier to use Trac with multiple projects, I think Trac should have a central configuration file (e.g., /etc/trac.ini) which contains defaults for all the options in the env trac.ini that are reasonable. These options can than be overwritten in env-specific trac.ini's.
Would this be as useful as I think? I could whip up a patch if necessary. :)
Patch that adds a CENTRAL_CONFIG var.