>you might just as well use any other file format for your config and call it a config file, not .env If you name it .env it's much easier to setup source cont

>you might just as well use any other file format for your config and call it a config file, not .env If you name it .env it's much easier to setup source control rules to exclude .env files. If you name them say .config, then you increase the chances of accidentally leaking creds (by checking them into the repo).