Suggestion: configure .env for each application

It would be useful to have a feature that sets the .env file, when cloning a staging environment.
To prevent misconfiguration or ambiguous environments, such as targeting common resources such as Redis.

By copying all files from Live to Staging these configuration problems can be harmful.

Otherwise specifying the .env from control panel in each application and protect from overwriting.

For WordPress sites there is an environment variable called WP_ENVIRONMENT_TYPE that is suppose to be set for the wp_get_environment_type function to be able to detect when a staging site is in use. It would be nice if they would set that environment variable whenever a staging site is created.