Opened 14 years ago

Closed 14 years ago

#7 closed enhancement (worksforme)

managing trac.ini

Reported by: Horst Meyerdierks Owned by: Horst Meyerdierks
Priority: major Milestone:
Component: trac Version:
Keywords: Cc:


A minority of web admin tasks affect the trac.ini file. This means we cannot implement another management procedure for those files without taking account of the concurrent management of the file by two procedures. One possible such procedure was to have the hourly cron job update trac.ini from the project's svn repository. This would overwrite changes made by web admin, and it might change trac.ini to owner root, whereafter web admin (www-data) would be unable to change it. Perhaps that is the solution, make the file root-owned so that web admin's attempts to change it fall over, thus encouraging developers to make those changes by hand in the svn repository. But how badly does it fall over?

Change History (1)

comment:1 by Horst Meyerdierks, 14 years ago

Resolution: worksforme
Status: newclosed

For the moment developers can use the full web admin plugin, so will sometimes change trac.ini. Typically this is when the default component, default milestone, etc. are changed. On the whole write access to the file from web admin is a minor issue. For the moment the only way to configure the bulk of trac.ini is by asking the superuser to vi the file for you.

Some time in the future we may have to change this. What is envisaged is that the project would have a master trac.ini in their repository and the superuser would check it out every hour to take effect. When we move to that scheme trac.ini would become owned by root and web admin would no longer be able to write to it. When web admin would attempt to do that a python traceback would result, which says that it did not have permission to write to the trac.ini file. That would have to serve as a reminder to the developer to do the necessary in the repository instead.

This would not make web admin obsolete, the bulk of administration does not involve trac.ini, but is and will remain to be possible trough web admin.

Note: See TracTickets for help on using tickets.