laravel4cookbook

Deployment 97
43 {
44 $options["type"] = "js";
45 $this->call("asset:minify", $options);
46 }
47 else
48 {
49 $this->call("asset:combine", $options);
50 }
51 }
52 }
53 }
54 }
.
This file should be saved as app/commands/BuildCommand.php.
The BuildCommand class fetches the asset lists, from the configuration files, and iterates over them;
combining/minifying as needed. It does this by checking file extensions. If the file ends in .min.js
then the minify command is run in js mode. Files ending in .min.css are minified in css mode, and
so forth.
The app/config/*/asset.php files are environment-based. This means running the build command
will build the assets for the current environment. Often this will not be the environment you want
to build assets for. I often build assets on my local machine, yet I want assets built for production.
When that is the case; I provide the –env=production flag to the build command.
Watching Assets
So we have the tools to combine, minify and even build our asset files. It’s a pain to have to remember
to do those things all the time (especially when files are being updated at a steady pace), so we’re
going to take it a step further by adding a file watcher.
Remember the Resource Watcher library we added to composer.json? Well we need to add it to the
list of service providers:
1 "providers" => [
2 // other service providers here
3 "JasonLewis\ResourceWatcher\Integration\LaravelServiceProvider"
4 ]