Modify ↓
Opened 18 years ago
Closed 17 years ago
#3538 closed enhancement (worksforme)
extension of trac.web.modpython_frontend to manage central configurations (trac instance independent)
| Reported by: | ThurnerRupert | Owned by: | Jonas Borgström |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.9.4 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
current status is:
- there is a central trac.ini, managed by editing the file
- there is a instance local InterMap (see also #3528)
- there is a webadmin plugin for managing a part of the instance local trac.ini
- there is a iniadmin plugin for managing the rest of the instance local trac.ini parameters
trac.ini/intermap would both greatly benefit from a central management/gui. one possibility to provide management for this could be to attach it to trac.web.modpython_frontend.
Attachments (0)
Note:
See TracTickets
for help on using tickets.
With 0.11, instead of a central trac.ini, each environment can specify a trac.ini file from which it inherits (see TracDev/ReleaseNotes/0.11).
If you actually inherit from a trac.ini that corresponds to a "central" Trac instance, you could effectively use that Trac's admin module to manage the trac.ini.
The question of the sharing of an InterMapTxt content has its own ticket, as you mentioned, and the question whether the iniadmin should be integrated in Trac core is yet another topic (should eventually be raised on the trac-dev mailing list).