How to Set external Parameters in the Service Container
Warning: You are browsing the documentation for Symfony 2.x, which is no longer maintained.
Read the updated version of this page for Symfony 7.1 (the current stable version).
In the article Configuring Symfony (and Environments), you learned how to manage your application configuration. At times, it may benefit your application to store certain credentials outside of your project code. Database configuration is one such example. The flexibility of the Symfony service container allows you to easily do this.
Environment Variables
Symfony will grab any environment variable prefixed with SYMFONY__
and
set it as a parameter in the service container. Some transformations are
applied to the resulting parameter name:
SYMFONY__
prefix is removed;- Parameter name is lowercased;
- Double underscores are replaced with a period, as a period is not a valid character in an environment variable name.
For example, if you're using Apache, environment variables can be set using the
SetEnv directive with the following VirtualHost
configuration:
1 2 3 4 5 6 7 8 9 10 11 12
<VirtualHost *:80>
ServerName Symfony
DocumentRoot "/path/to/symfony_2_app/web"
DirectoryIndex index.php index.html
SetEnv SYMFONY__DATABASE__USER user
SetEnv SYMFONY__DATABASE__PASSWORD secret
<Directory "/path/to/symfony_2_app/web">
AllowOverride All
Allow from All
</Directory>
</VirtualHost>
For Nginx web servers, the environment variables can be set with the fastcgi_param
directive. For example, in the configuration file where the fastcgi_params
file is included:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
server {
server_name domain.tld www.domain.tld;
root /var/www/project/web;
location / {
try_files $uri /app.php$is_args$args;
}
location ~ ^/app\.php(/|$) {
fastcgi_pass unix:/var/run/php5-fpm.sock;
fastcgi_split_path_info ^(.+\.php)(/.*)$;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
fastcgi_param DOCUMENT_ROOT $realpath_root;
fastcgi_param SYMFONY__DATABASE__USER user;
fastcgi_param SYMFONY__DATABASE__PASSWORD secret;
internal;
}
# ...
}
Note
The examples above are for an Apache and Nginx configuration. However, this will work for any web server which supports the setting of environment variables.
Also, in order for your console to work (which does not use a web server), you must export these as shell variables. On a Unix system, you can run the following:
1 2
$ export SYMFONY__DATABASE__USER=user
$ export SYMFONY__DATABASE__PASSWORD=secret
Now that you have declared an environment variable, it will be present
in the PHP $_SERVER
global variable. Symfony then automatically sets all
$_SERVER
variables prefixed with SYMFONY__
as parameters in the service
container.
You can now reference these parameters wherever you need them.
1 2 3 4 5 6
doctrine:
dbal:
driver: pdo_mysql
dbname: symfony_project
user: '%database.user%'
password: '%database.password%'
Constants
The container also has support for setting PHP constants as parameters. See Introduction to Parameters for more details.
Miscellaneous Configuration
The imports
directive can be used to pull in parameters stored elsewhere.
Importing a PHP file gives you the flexibility to add whatever is needed
in the container. The following imports a file named parameters.php
.
1 2 3
# app/config/config.yml
imports:
- { resource: parameters.php }
Note
A resource file can be one of many types. PHP, XML, YAML, INI, and
closure resources are all supported by the imports
directive.
In parameters.php
, tell the service container the parameters that you wish
to set. This is useful when important configuration is in a non-standard
format. The example below includes a Drupal database configuration in
the Symfony service container:
1 2 3
// app/config/parameters.php
include_once('/path/to/drupal/sites/default/settings.php');
$container->setParameter('drupal.database.url', $db_url);