在Symfony2中，哪里是存储app wide参数的正确位置？

Question

I'd like to store a few application specific values for example:

• a default Id number for a particular user choice if it's not set yet
• keys/tokens/secrets for various services API's like facebook or flickr

Closest I've found so far is http://symfony.com/doc/2.0/cookbook/bundles/best_practices.html#configuration

If I used app/config/parameters.ini it would look like:

[flickr]
    callbackUrl = http://example.com/approve
    requestTokenUrl = http://www.flickr.com/services/oauth/request_token
    consumerKey = 123a1237a29b123a5541232e0279123

[app]
    default_layout = 2

these should be available in different bundles and also in templates

Answer 1

these should be available in different bundles and also in templates

They are. As long as you can access the container, you can access the parameters. From the docs you linked to: $container->getParameter('acme_hello.email.from');

I think there's an error in your parameters.ini example. 'flickr' and 'app' shouldn't be wrapped in brackets. Also, the first element of parameters.ini should be [parameters] .

Personally, I like using an app.yml file because I'm used to using it in Symfony 1.x projects (and because I don't see the reason for using an .ini file.). You can create app/config/app.yml and import it into your app/config/config.yml file like this:

imports:
    - { resource: app.yml }

Your app.yml would look like this:

parameters:
  flickr:
    callbackUrl:     http://example.com/approve
    requestTokenUrl: http://www.flickr.com/services/oauth/request_token
    consumerKey:     123a1237a29b123a5541232e0279123

  app:
    default_layout:  2

And this is how you would access data: $container->getParameter('flickr.callbackUrl');

A third option is to define your parameters directly in app/config/config.yml . The code would be exactly the same as my example for app/config/app.yml . I don't recommend doing this though because app/config/config.yml can get pretty filled up with bundle configuration parameters, and I think it's cleaner to keep your own app params in a separate file. But of course, it's all up to you.