laravel4cookbook

Multisites 202
Note on Running Commands in Local Environment
The moment you add multiple environments to your application, you create the possibility that
artisan commands might be run on the incorrect environment.
Just because Laravel 4 is capable of executing in the correct environment doesn’t mean you will
always remember which environment you are in or which environment you should be in…
Start learning to provide the environment for every artisan command, when you’re working with
multiple environments. It’s a good habit to get into.
Using Site-Specific Views
One of the benefits of multiple environment-specific configuration sets is that we can load different
views for different sites. Let’s begin by creating a few:
1 127.0.0.1 dev.www.tutorial-laravel-4-multisites
2 127.0.0.1 dev.admin.tutorial-laravel-4-multisites
.
This was extracted from /etc/hosts.
You can really create any domains you want, but for this part we’re going to need multiple domains
pointing to our testing server so that we can actually see different view files being loaded, based on
domain.
Next, update your app/bootstrap/start.php file to include the virtual host domains you’ve created:
1 $env = $app->detectEnvironment([
2 "www" => ["dev.www.tutorial-laravel-4-multisites"],
3 "admin" => ["dev.admin.tutorial-laravel-4-multisites"]
4 ]);
.
This was extracted from /bootstrap/start.php.
.
Phil Sturgeon made an excellent point about not using URL’s to toggle environments, as somebody
can easily set a hostname to match your development environment and point it to your production
environment to cause unexpected results. This can lead to people gleaning more information than