title: Changing default environment in Laravel 4
body: <p>In Laravel 4 the default configuration environment is 'production'. This means that if you run an artisan command without the <code>--env</code> option, it assumes the production configuration. This can be seen in <code>\Illuminate\Foundation\Application::detectWebEnvironment()</code> which is called by <code>detectConsoleEnvironment()</code> when no <code>--env</code> option is set.</p>
  
  <p>This behavior has become a risk with my development environment. It's really easy to forget the --env option and, say, unintentionally run a migration on your production database. (Yes, that happened but thankfully it was a minor change.) I'm close to just renaming my production environment config to 'real-production' but it seems like there should be a more elegant solution. </p>
  
  <p><strong>TL;DR</strong></p>
  
  <p>How can I change the default environment in Laravel 4 such that artisan commands do not run on production by default?</p>