Change the EnvConfigurator to only handle the .env file

[dunglas]

Companion PR for symfony/recipes#466 and symfony/symfony#28533.

As explained in symfony/recipes#466 (comment), it will require to tag a v2 to prevent problems with previous installation.

In a next PR, we may want to allow recipes to add values in specific environment env files (such as .env.test. It will require to tweak a bit the Flex server. I'm not sure that it's really needed.

[maxhelias]

In this case, would not it be more prudent to merge it on a branch dev to prepare a new version ?
Because for this PR, this implies a change of Git workflow for the devs because the advantage of the .env.dist file is that it is versioned.

Or I suggest defining a system like symfony/symfony#28533 to edit all environments and have a recipe structure like this for add values in specific environment :

"env" : {
   "dev": {
      // ...
   },
   "test": {
     // ...
   }
}

We would just have to make conditions on the keys in the env configurator without creating a break change.

WDYT?

[dunglas]

Because for this PR, this implies a change of Git workflow for the devs because the advantage of the .env.dist file is that it is versioned.

Now it's the .env file that is versioned. The developper can override it by using a .env.local file that isn't versioned. See https://github.com/symfony/recipes/pull/466/files#diff-48a706859e5c9d4e903b5065baa57726R21

Or I suggest defining a system like symfony/symfony#28533 to edit all environments and have a recipe structure like this for add values in specific environment :

This PR already requires symfony/symfony#28533 to be merged! The config you propose would be fine, but in another PR (probably after 4.2, as it requires to modify the Flex server, on the hand the current PR works with the current server).

without creating a break change.

Actually, we need the breaking because of this: symfony/recipes#466 (comment)

[ogizanagi]

Now that symfony/symfony#28533 is merged, we can move forward here and in symfony/recipes#466 :)

[nicolas-grekas]

I'm not sure we need this PR anymore.
Instead, I'd suggest doing just one thing: when a .env.test file is found, skip updating phpunit.xml files.
And keep all the other behaviors identical.

[dunglas]

Closing in favor of #434