- 🇳🇱Netherlands kingdutch
In my recent blogpost (Web Archive Link) I've outlined how this comes essentially for free with ✨ Use symfony/runtime for less bespoke bootstrap/compatibility with varied runtime environments Active while providing end-users an easy way to swap out the logic if needed.
[The Symfony Runtime Component usage] provides us with a standardised way to get the environment name regardless of what kind of application you're building. For the initial Runtime implementation we may even resolve the $environment variable statically to prod to mimic the current behavior. That would allow work to be done in [this issue] to determine the name of the variable that sets the environment and then provide this as an update to Drupal websites without having to touch their front-controllers again. Alternatively if they're unhappy with how Drupal determines the environment, then they can overwrite the runtime to resolve this variable themselves, without having to touch the front-controller.