Easiest thing to do is read the official documentation- it's based on a community plugin called DotEnv:

https://github.com/vlucas/phpdotenv

The basics are to just create file called .env in the root of your project, and set any variables you need.

You can then reference them using the function dotenv('variable_name') and you're good to go.

The only key thing is that the .env file is environment specific and should not be checked-in as part of your code repository.

jayhealey said:

Easiest thing to do is read the official documentation- it's based on a community plugin called DotEnv:

https://github.com/vlucas/phpdotenv

The basics are to just create file called .env in the root of your project, and set any variables you need.

You can then reference them using the function dotenv('variable_name') and you're good to go.

The only key thing is that the .env file is environment specific and should not be checked-in as part of your code repository.

But how to use two different env's and select them? For example one for production and other for local development?

But how to use two different env's and select them? For example one for production and other for local development?

http://laravel.com/docs/5.0/configuration

Note: Instead of 'dotenv()', use Laravel's helper 'env()'.

On my local setup I have a .env with local settings and on my production server I have the same .env file with production credentials/values.