Various ways to set variables
Platform.sh has always prided itself on offering our customers as much flexibility to control their own projects as we can. What language to use, what services to use, how the server should be configured, what applications to run, all of these are under the user's control. We even allow users to set various control variables and environment variables per-environment.
And now there's even another way to set them, via your application configuration file.
Platform.sh's variable support is designed to allow users to set per-environment configuration (such as API keys for 3rd party services) as well as to control aspects of the environment. Some applications, though, have their own environment variables they rely on for various reasons, such as to set a dev/prod toggle or control a build process. Those generally shouldn't vary by environment.
For that reason it's now possible to set variables from
.platform.app.yaml. Those values will be tracked in Git just like the rest of your code base, keeping all of the important bits in the same place.
If you're using PHP, you can even use this system to set
php.ini values. Need to change your memory limit? Set a prepend file? Control the error reporting level? That can all be done now directly from the
For environment variables that should change per-environment or contain sensitive information the current mechanism (setting variables through the UI or using the CLI tool) nothing changes. Your current workflow is fine.