laravel4cookbook

Deployment 72
1 "jasonlewis/resource-watcher" : "dev-master"
.
This was extracted from composer.json.
Once these requirements are added to the composer.json file, we need to update the vendor folder:
1 composer update
We’ll look at how to integrate these into our deployment workflow shortly.
Environment Commands
Environments are a small, yet powerful, aspect of any Laravel 4 application. They primarily allow
the specification of machine-based configuration options.
There are a few things you need to know about environments, in Laravel 4:
1. The files contained in the root of app/config are merged or overridden by environment-based
configuration files.
2. Configuration files that are specific to an environment are stored in folders matching their
environment name.
3. Environments are determined by an array specified in bootstrap/start.php and are matched
according to the name of the machine on which the application is being run.
4. An application can have any number of environments; each with their own configuration
files. There can also be multiple machine names (hosts) in each environment. You can have
two staging servers, a production server and a testing server (for instance). If their machine
names match those in bootstrap/start.php then their individual configuration files will be
loaded.
5. All Artisan commands can be given an –env option which will override the environment
settings of the machine on which the commands are run. I’m sure there are other ways in
which environments affect application execution, but you get the point: environments are a
big-little thing.
Checking Environments
As I mentioned earlier; environments are usually specified in boostrap/start.php. This is probably
going to be ok for the 99% of Laravel 4 applications that will ever be made, but we can improve upon
it slightly still.