On Sun, Mar 8, 2009 at 7:30 AM, Jeff Hammel <[email protected]> wrote:
> > 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. > I would certainly have issues if my configuration wasn't persistent--the scope of information is not that different. You could think of the permissions as configuration data, why not put that in trac.ini? For me the argument is all about amount of effort for coding this vs. who the user is (in this case the person doing the installation and admin tasks). For Trac, it seems like the user can be expected to edit an ini file, even if it can be somewhat complex. However, this is a bit of a barrier for non-technical users. These are the users Wordpress is targetted at (yes, it's nominally a blog package, but there are wiki plugins and maybe even issue tracker plugins), and all they have to do is unzip packages and enter database connection information. An ini file is only "easy" in that you can open it with a text editor. A good web interface should match an ini file in the ease-of-use category any day. The part of the web interface that is hard is writing the code and tools...which has not been a priority/itch for anyone yet. Ted --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
