Support template version of site_xxx.cs files for new projects

[jouvin@…]

At LAL, we are using a customized version of site_xxx.cs files for every project to include support for some local configuration options (like loading TracNav.css in every project from site_css.cs).

Unfortunatly current version of trac-admin create those files from hardcoded values in module trac.web.chrome. It would be nice to have this module check for existence of a template version of these files and use them if they are available. And keep hardcoded values as a fallback in case there is no template version available.

I would be even nicer if location of these template site_xxx.cs files could be defined in the global trac.ini file.

Along the same lines, when creating the project trac.ini, current version of trac-admin uses the option values defined in global trac.ini. IMO, it should not defined them at all (to allow for global changes) or defined them commented out.

[anonymous]

Regarding settings in the central trac.ini: I agree, and comment here although it probably should be a separate ticket…

The central trac.ini file is a great improvement for supporting many projects, but by copying the settings locally on new projects some of the purpose is defeated as any new installations have to be "cleaned" before made available.

I am sure my needs are not like everyone elses, so having an option would probably be the best alternative. Default behavior should be not to copy, but have a --copysettings option to override. Also supported in command line interface:

Global settings exists. Do you want to copy these settings to <new environment>? (y/n - default no)

[Christopher Lenz]

(Moving non-trivial enhancements to next milestone)

[osimons]

Trac is currently at 0.11b1, and the site_xxx.cs templates are gone - replaced by a Genshi site.html that provides much more flexibility. It will also allow to keep a central site.html (via [inherit] templates_dir option) with a full range of dynamic features. Even including other files at will - include a site2.html if that exists in the project for instance.

As for settings when creating a new project, this is now possible in a slightly different manner as :

trac-admin /path/to/new/env initenv --inherit=/path/to/global/trac.ini

See #5651 & [6226] for details on that.

Closing as 'wontfix' in response to your specific requests for old Trac version - although it can be seen as 'fixed' in current trunk based on your actual needs…