Confusion with .env and config files

The .env file prevail on everything. The way I see it is the app/Config/ directory contains the settings for your dev environment because you don't want your production settings saved in your source control repository. So on your production server you add a .env file that overrides the default settings and is not overwritten when you push an update.

Thanks for your reply. In such a case, I will then just add the .env on my .gitignore, and I create a .envProduction file, so when I deploy the site I will not replace the production .env file. Using the config files will just confuse me.

Once again, thanks for your advice.