Working with Configuration Files

A follow-up question.

So, if I understand correctly, given the very typical development + production environments setup, each would need their own .env file. That feels a bit fragile to me because it would be far too easy to accidentally overwrite the production version with the dev version during an FTP upload for instance. (Something I used to do on a regular basis with config.php before I figured out how to properly handle multiple environments under v3.   )

Is there any way to leverage the /Config/Boot environment specific files to manage values as set in the Config\App, Config\Database, etc. namespaces?