This cookbook entry appeared recently and thought it was worth mentioning in regards to environment variables and $_SERVER: http://symfony.com/doc/current/cookbook/configuration/external_parameters.html
On May 15, 7:24 pm, ryan weaver <[email protected]> wrote: > It does seem strange that XML (and of course PHP) support the constant > functionality, but YAML does not. > > But, I don't feel too strongly either way, since you can easily include on > parameters.xml or parameters.php file from your config.yml file and take > care of everything in there. So, it would help a little bit, but it's not > quite solving a problem. > > Ryan Weaver > US Office Head & Trainer - KnpLabs - Nashville, > TNhttp://www.knplabs.com<http://www.knplabs.com/en>http://www.thatsquality.com > Twitter: @weaverryan > > > > > > > > On Thu, May 12, 2011 at 2:41 PM, Beau Simensen <[email protected]> wrote: > > The issue with the way you propose is the parameters set this way cannot > > come from anywhere else than the environment and that only parameters > > designed to come from the environment can be defined this way. this is a > > major limitation compared to the current way which allows you to redefine > > *any* parameter by using an environment variable. > > > This makes sense and is very nice, but if I'm writing an application and I > > know that I need to have a variable set to specify an external resource > > somehow, it would be nice to just be able to specify it in the configuration > > as such. It becomes clear in that case that this information is going to be > > passed in from an external source. > > > Is there any harm in supporting both? > > > How does %CONSTANT:*% sound for handling constants? Would this be a good > > solution? It sounds like (from > > bshaffer<https://github.com/bshaffer/symfony-docs/commit/2bdd4fb99ade82194618c...>) > > that YAML can't support constants currently without changing the syntax. It > > can be supported in addition to the existing type="constant" XML support. > > > -- > > If you want to report a vulnerability issue on symfony, please send it to > > security at symfony-project.com > > > 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 -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
