amazon web services - Laravel and environment variables in command line production without .env file -


when upgraded laravel 5 started using env system set configurations inside file @ root.

.env

db_host=x.x.x.x.x db_username ... 

this file not part of repo , when deploy set same variables onto system environment variables (using amazon beanstalk here) accessible without need of .env file.

so works when use command line in scripts in production these system environment variables don't seem accessible in command line. accessible when php served through web server.

i found if copy add .env file works in command line that's why i'm confused, thought system prevent committing sensitive information repo , seems have so can use php artisan migrate , other commands in production.

am missing something? there way system environment variables available in command line or have somehow create .env file dynamically in production?

i thought .env file part of setting server. .env file ignored git, once it's setup, can push/pull heart's content , it'll leave .env file alone. that's @ least how i've done far.


Comments

Popular posts from this blog

PHP DOM loadHTML() method unusual warning -

python - How to create jsonb index using GIN on SQLAlchemy? -

c# - TransactionScope not rolling back although no complete() is called -