True, but using app.yml allows you to set system wide defaults and then override them as necessary within an application without having to write any code.
Joby Walker synace wrote: > Yes, but 'app.yml' implies it's application specific. > > Since changing the use of config/config.php, project-wide configuration > is much more complex now. > > There are people who would use this. (Especially n00bs) > http://www.symfony-project.com/forum/index.php/m/15021/#msg_15021 > http://www.symfony-project.com/forum/index.php/m/14363/#msg_14363 > > ~synace > > -----Original Message----- > From: [email protected] > [mailto:[EMAIL PROTECTED] On Behalf Of Joby Walker > Sent: Friday, November 03, 2006 2:40 PM > To: [email protected] > Subject: [symfony-devs] Re: (Enhancement) Project-wide configuration > file > > > > While I disagree with Fabien (project wide configuration is very useful > -- DRY), I don't see a need for this. You can just add an app.yml in > the base config/ directory and you end up with the same result. > > Joby Walker > > > Fabien POTENCIER wrote: >> -1 >> >> I don't think there is a real need for project wide configuration... >> but >> this is just my opinion and my current usage of symfony. >> >> Fabien >> >> synace wrote: >>> Addition of a project.yml file in the /config directory for turn-key >>> project-wide settings. This replaces the old way of putting config >>> settings into /config/config.php now that it is loaded before the >>> symfony classes. >>> >>> http://www.symfony-project.com/trac/ticket/1036 >>> >>> >>> + or - please. >>> >>> ~synace >>> >>> >>> >>> > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
