It’s a common thing to use environment variables to configure Symfony for dev, staging, production… It allows to define specific configurations such as database host username and password, api entrypoint, … without saving those information into files and commiting them,… it’s a bad practice and could lead to security problems.
With Apache you can forward variables with this kind of configuration inside your host (it supposes that environment variables are defined on your system) :
It allows you to use Symfony through CLI or web pages and use the correct configurations.
Nginx / PHP-FPM
With Nginx and more exactly with PHP-FPM, it’s no so easy because of the default PHP-FPM configuration:
# clear_env boolean
Clear environment in FPM workers. Prevents arbitrary environment variables from reaching FPM worker processes by clearing the environment in workers before env vars specified in this pool configuration are added. Since PHP 5.4.27, 5.5.11, and 5.6.0. Default value: Yes.
So by default all environment variables are cleared and not forwarded to PHP.
At this point, there are two ways to pass variables to your Symfony application,
both modifying the PHP-FPM pool config file
(could be a custom pool):
- Define all your env variables yourself at the end of the file:
- Modify the default value of the
clear_envconfiguration to No and you will have access to all env vars in your PHP application once php-fpm restarted.
Do not forget to remove the comma at the beginning of the line
If you use docker you could add this
RUN command in your
Dockerfile to change de default php-fpm configuration
Rebuild your Docker image !!
With Symfony production environment you will probably DO NOT have to forward those environment variables in your virtual hosts files, because the cache is warmed up thanks to a CLI command… and… your variables are probably already defined in your CLI/shell system:
- docker/docker-compose environment variables