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?

I'm not sure if I understand you correctly, - but I may mention an implementation which covers my needs very well. I've an app which I deploy on multiple sites, - which has different configurations. I've customized the index.php. Based on a logic where I look for a folder under config which has a name equal the current hostname using the gethostname() function. If the "hostname" folder exist, - all configuration files are read from this folder. If the folder doesn't exist, - default config files are read from /config. I feel this is a very flexible solution.

Attached Files

Thumbnail(s)