What's the difference between project.yml and app.yml (in project level)? If none, I think it's better not to bring it in because it can also bring confusion. I understand the name project.yml is clearer than app.yml in project level, but as one characteristic of symfony is the "overriding" behavior of the configuration files, I consider reasonable to treat project/app.yml as the "default application settings in project level" -- then project.yml looks a bit redundant. So I prefer app.yml over project.yml, but agree with that the documentation about the availability of such file at project level is welcome.
Tamcy On Nov 8, 6:20 am, "synace" <[EMAIL PROTECTED]> wrote: > I agree with that. If app.yml is and will always be supported in > /config/app.yml, then we should add some clear documentation on how to > best utilize in the manner described. > > Though, since 'project.yml' is and would be optional, we can have our > cake and eat it too.. > > project.yml -> project-wide, non-overridable configuration options > app.yml -> project wide when in /config, overridable in > /apps/xxxxx/config > > I'm personally using app.yml right now until the project.yml patch is > in. > > ~synace > > -----Original Message----- > From: [email protected] > > [mailto:[EMAIL PROTECTED] On Behalf Of Joby Walker > Sent: Tuesday, November 07, 2006 5:05 PM > To: [email protected] > Subject: [symfony-devs] Re: (Enhancement) Project-wide configuration > file > > 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 -~----------~----~----~----~------~----~------~--~---
