only one .env file for local, staging and production?

i have different passwords on all stages. I have different settings too in the .env file.

What I end up doing is to upload the .env file manually after a file change to the stage, manually setting the correct passwords and keys. is there no better way, maybe official laravel way?

so again:

i say have: .env

DB_DATABASE=myDBnameLocal
DB_USERNAME=myuserLOCAL
DB_PASSWORD=mypasswordLOCAL

different values for staging etc

I rather have 3 different files, and a 4th file where I set the environment to

say a .stage where I define which environment my app is in. And depending on that value, I load the correct .env file.

is there a way to do something like this or is there a way to do it different altogether?

say define all passwords in one big file and call things like this:

DB_DATABASE_LOCAL=myDBnameLocal
DB_USERNAME_LOCAL=myuserLOCAL
DB_PASSWORD_LOCAL=mypasswordLOCAL

DB_DATABASE_PRODUCTION=myDBnamePRODUCTION
DB_USERNAME_PRODUCTION=myuserPRODUCTION
DB_PASSWORD_PRODUCTION=mypasswordPRODUCTION

even though this does not seem to be very safe.

from Newest questions tagged laravel-5 - Stack Overflow http://ift.tt/2l5Vp2b
via IFTTT