On Sun, Mar 08, 2009 at 10:19:14AM +0200, anatoly techtonik wrote: > > On Sat, Mar 7, 2009 at 7:02 PM, Evan Dower <[email protected]> wrote: > > > > This brings up something that has been kind of confusing for me. Why > > do we keep so much information in the environment config file? > > Because config file is something you can edit remotely and uniformly > through the shell script without resolving to mysqladmin, sqliteadmin > or whatever admin you need to access you DB. Even trac-admin is not > that intuitive as plain text file. In addition, text file > configuration can be shared among various utility applications - not > necessary written in Python. You may make an emergency backup of your > config even if Python on server get lost or your DB failed. > > -- > --anatoly t.
A hearty +1 to all of this. Changing configuration through the ini file is amazingly simple. While complex configurations result in large files, I'll trade those disadvantages for the transparency and ease afforded from keeping this configuration out of the database. The scope is different too. Databases are for persistant information and the trac.ini file is for configuration. Jeff --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
