framework: .env is not loaded when .env.testing is

You could even add some crazy extends features. :feelsgood:

@extends(.env)

DB_DATABASE=testing

Yes only 1 file is loaded, and by override values we mean it’ll load the values from that file not the .env file.

Sounds like a great PR. 😃

When you are creating a new .env file, all the configuration you need to generate should be specific to that file. Since .env.testing is for testing only, you should always a APP_KEY for .env.testing like:

php artisan key:generate --env=testing

.env files are present on production environments too, it’s not only for development. And you may still miss the point: if that’s the way it works, the documentation shouldn’t say it otherwise.

Man the documentation is really confusing on this point.

This file will override values from the .env file when running PHPUnit tests

In fact it doesn’t override values from the .env file. It doesn’t depend on the .env file at all. Am I missing something?

So how are we supposed to override values that are in .env.testing when running tests?

I know that in phpunit.xml you can have testing defaults and override those with an unversioned .env.testing file. But that only works for PHPUnit.

I would rather have .env.testing versioned so that I could run a fresh migration of the test db just by running APP_ENV=testing php artisan migrate:fresh.

But then that brings about the problem that I could only have a single set of test db credentials there, and my colleagues wouldn’t have any simple way to override them if their local db is using a different username, password or db name.

Might be best for someone to simply craft a PR to make this documentation a little more clear?

It is not necessarily an error in my opinion with the framework. My opinion is that env files are for development purposes only.

@themsaid @GrahamCampbell Your thoughts?

@m1guelpf Yes, sorry for that, I’ve fixed the description!