Environment Variable Processors
Warning: You are browsing the documentation for Symfony 4.x, which is no longer maintained.
Read the updated version of this page for Symfony 7.1 (the current stable version).
Using env vars to configure Symfony applications is a common practice to make your applications truly dynamic.
The main issue of env vars is that their values can only be strings and your
application may need other data types (integer, boolean, etc.). Symfony solves
this problem with "env var processors", which transform the original contents of
the given environment variables. The following example uses the integer
processor to turn the value of the HTTP_PORT
env var into an integer:
1 2 3 4
# config/packages/framework.yaml
framework:
router:
http_port: '%env(int:HTTP_PORT)%'
Built-In Environment Variable Processors
Symfony provides the following env var processors:
env(string:FOO)
-
Casts
FOO
to a string:1 2 3 4 5
# config/packages/framework.yaml parameters: env(SECRET): 'some_secret' framework: secret: '%env(string:SECRET)%'
env(bool:FOO)
-
Casts
FOO
to a bool (true
values are'true'
,'on'
,'yes'
and all numbers except0
and0.0
; everything else isfalse
):1 2 3 4 5
# config/packages/framework.yaml parameters: env(HTTP_METHOD_OVERRIDE): 'true' framework: http_method_override: '%env(bool:HTTP_METHOD_OVERRIDE)%'
env(int:FOO)
-
Casts
FOO
to an int. env(float:FOO)
-
Casts
FOO
to a float. env(const:FOO)
-
Finds the const value named in
FOO
:1 2 3 4 5 6
# config/packages/security.yaml parameters: env(HEALTH_CHECK_METHOD): 'Symfony\Component\HttpFoundation\Request::METHOD_HEAD' security: access_control: - { path: '^/health-check$', methods: '%env(const:HEALTH_CHECK_METHOD)%' }
env(base64:FOO)
-
Decodes the content of
FOO
, which is a base64 encoded string. env(json:FOO)
-
Decodes the content of
FOO
, which is a JSON encoded string. It returns either an array ornull
:1 2 3 4 5
# config/packages/framework.yaml parameters: env(TRUSTED_HOSTS): '["10.0.0.1", "10.0.0.2"]' framework: trusted_hosts: '%env(json:TRUSTED_HOSTS)%'
env(resolve:FOO)
-
If the content of
FOO
includes container parameters (with the syntax%parameter_name%
), it replaces the parameters by their values:1 2 3 4 5 6 7
# config/packages/sentry.yaml parameters: env(HOST): '10.0.0.1' sentry_host: '%env(HOST)%' env(SENTRY_DSN): 'http://%sentry_host%/project' sentry: dsn: '%env(resolve:SENTRY_DSN)%'
env(csv:FOO)
-
Decodes the content of
FOO
, which is a CSV-encoded string:1 2 3 4 5
# config/packages/framework.yaml parameters: env(TRUSTED_HOSTS): "10.0.0.1,10.0.0.2" framework: trusted_hosts: '%env(csv:TRUSTED_HOSTS)%'
env(file:FOO)
-
Returns the contents of a file whose path is the value of the
FOO
env var:1 2 3 4 5
# config/packages/framework.yaml parameters: env(AUTH_FILE): '../config/auth.json' google: auth: '%env(file:AUTH_FILE)%'
env(require:FOO)
-
require()
the PHP file whose path is the value of theFOO
env var and return the value returned from it.1 2 3 4 5
# config/packages/framework.yaml parameters: env(PHP_FILE): '../config/.runtime-evaluated.php' app: auth: '%env(require:PHP_FILE)%'
4.3
The
require
processor was introduced in Symfony 4.3. env(trim:FOO)
-
Trims the content of
FOO
env var, removing whitespaces from the beginning and end of the string. This is especially useful in combination with thefile
processor, as it'll remove newlines at the end of a file.1 2 3 4 5
# config/packages/framework.yaml parameters: env(AUTH_FILE): '../config/auth.json' google: auth: '%env(trim:file:AUTH_FILE)%'
4.3
The
trim
processor was introduced in Symfony 4.3. env(key:FOO:BAR)
-
Retrieves the value associated with the key
FOO
from the array whose contents are stored in theBAR
env var:1 2 3 4 5
# config/services.yaml parameters: env(SECRETS_FILE): '/opt/application/.secrets.json' database_password: '%env(key:database_password:json:file:SECRETS_FILE)%' # if SECRETS_FILE contents are: {"database_password": "secret"} it returns "secret"
env(default:fallback_param:BAR)
-
Retrieves the value of the parameter
fallback_param
when theBAR
env var is not available:1 2 3 4 5
# config/services.yaml parameters: # if PRIVATE_KEY is not a valid file path, the content of raw_key is returned private_key: '%env(default:raw_key:file:PRIVATE_KEY)%' raw_key: '%env(PRIVATE_KEY)%'
When the fallback parameter is omitted (e.g.
env(default::API_KEY)
), then the returned value isnull
.4.3
The
default
processor was introduced in Symfony 4.3. env(url:FOO)
-
Parses an absolute URL and returns its components as an associative array.
1 2
# .env MONGODB_URL="mongodb://db_user:db_password@127.0.0.1:27017/db_name"
1 2 3 4 5 6 7 8 9 10 11
# config/packages/mongodb.yaml mongo_db_bundle: clients: default: hosts: - { host: '%env(string:key:host:url:MONGODB_URL)%', port: '%env(int:key:port:url:MONGODB_URL)%' } username: '%env(string:key:user:url:MONGODB_URL)%' password: '%env(string:key:pass:url:MONGODB_URL)%' connections: default: database_name: '%env(key:path:url:MONGODB_URL)%'
Caution
In order to ease extraction of the resource from the URL, the leading
/
is trimmed from thepath
component.4.3
The
url
processor was introduced in Symfony 4.3. env(query_string:FOO)
-
Parses the query string part of the given URL and returns its components as an associative array.
1 2
# .env MONGODB_URL="mongodb://db_user:db_password@127.0.0.1:27017/db_name?timeout=3000"
1 2 3 4 5 6
# config/packages/mongodb.yaml mongo_db_bundle: clients: default: # ... connectTimeoutMS: '%env(int:key:timeout:query_string:MONGODB_URL)%'
4.3
The
query_string
processor was introduced in Symfony 4.3.
It is also possible to combine any number of processors:
1 2 3 4 5 6 7 8 9
# config/packages/framework.yaml
parameters:
env(AUTH_FILE): "%kernel.project_dir%/config/auth.json"
google:
# 1. gets the value of the AUTH_FILE env var
# 2. replaces the values of any config param to get the config path
# 3. gets the content of the file stored in that path
# 4. JSON-decodes the content of the file and returns it
auth: '%env(json:file:resolve:AUTH_FILE)%'
Custom Environment Variable Processors
It's also possible to add your own processors for environment variables. First, create a class that implements EnvVarProcessorInterface:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
use Symfony\Component\DependencyInjection\EnvVarProcessorInterface;
class LowercasingEnvVarProcessor implements EnvVarProcessorInterface
{
public function getEnv($prefix, $name, \Closure $getEnv)
{
$env = $getEnv($name);
return strtolower($env);
}
public static function getProvidedTypes()
{
return [
'lowercase' => 'string',
];
}
}
To enable the new processor in the app, register it as a service and
tag it with the container.env_var_processor
tag. If you're using the
default services.yaml configuration,
this is already done for you, thanks to autoconfiguration.