[Bug] Migration doesn't respect current environment

[jackmcdade]

Correct me if i'm wrong, but shouldn't the migrate command respect the current environment? I need to add the --env=local flag every time i run a migration.

[jasonlewis]

I think that's expected behavior. Could be wrong though.

[niallobrien]

I just ran into this issue too and it is a little annoying.
Perhaps it would be better if there was a default environment config option somewhere...?

[jackmcdade]

Seems strange to be a default behavior if i've got through the trouble (well, not that much trouble) of creating an environment rule and overriding configs. I would naturally expect commands to respect that.

[niallobrien]

@jackmcdade Well, it's not something that's currently configurable through local config files, but perhaps it should be?
Then we could just specify --env=prod when we want.

[jackmcdade]

You could "hack" the detectConsoleEnvironment() method in `vendor/laravel/framework/src/Illuminate/Foundation/Application.php' to return your desired environment, and pull it out later. I hate that kind of stuff though.

[franzliedke]

Can't you just set a global environment variable LARAVEL_ENV in your operating system? After all, you're always going to be in development mode on your local machine.

[jackmcdade]

The console is explicitly looking for "--env=" in your command to look for an environment, else it's always production. No other conditions are present.

[niallobrien]

@jackmcdade Any nice way to overload that method for local development?

[franzliedke]

Then I'd suggest falling back to an environment variable first. So that would be first --env option, then LARAVEL_ENV environment variable and lastly production.

[taylorotwell]

How did you specify the environment in the start file? Did you use a machine name?

[jackmcdade]

Yes, machine name in the start file.

[taylorotwell]

This is fixed. Thanks!