Changes between Initial Version and Version 7 of Ticket #1051
- Timestamp:
- Sep 7, 2005, 11:20:49 PM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1051
- Property Status new → assigned
- Property Component general → mod_python frontend
- Property Summary Trac needs a central config file → centralized trac.ini
- Property Priority normal → low
- Property Milestone 0.9
- Property Owner changed from to
-
Ticket #1051 – Description
initial v7 1 I was just trying to trick the [ TracModPython 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.1 I was just trying to trick the [wiki:TracModPython 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. 2 2 3 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.3 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. 4 4 5 5 Would this be as useful as I think? I could whip up a patch if necessary. :)
