On 26.06.2013 22:46, Apache Bloodhound wrote: > What was the reasoning behind the decision that the product configs should > be stored in the database instead of the .ini files? File configs would > allow us to reuse trac functionality for detecting modification of > configuration.
Config files are evil. It's IMO a crazy idea to use config files when, at the same time, you have a database available; because making atomic changes on the filesystem and the database at the same time is hard and error prone. And taking the long view, the existence of config files makes it much harder to contemplate porting BH to a distributed platform (e.g., GoogleAppEngine). I'd have expected, with all the pluggable architecture, that configuration change listener would be just another interface and it wouldn't matter where you actually store the config -- and that trac_admin would trigger an event in tracd instead of the latter having to poll the filesystem. -- Brane -- Branko Čibej | Director of Subversion WANdisco // Non-Stop Data e. [email protected]
