laravel4cookbook

Deployment
There are few things which have improved my life quite as much as learning how to create a custom
deployment process for my projects. Nothing is worse than having to worry about how to get your
files onto a remote server, when you’ve got an important bug to fix.
.
The code for this chapter can be found at: https://github.com/formativ/tutorial-laravel-4-
deployment
Deployment processes are one of the most subjective things about development. Everyone’s got their
own ideas about what should and shouldn’t be done. There are sometimes best practises; though
these tend only to apply to subsets of the whole process.
Things get even more tricky when it comes to deploying Laravel 4 applications because there aren’t
really any best practises to speak of, when it comes to working with remote servers and deploying
code.
Remember this as you continue — this tutorial isn’t the only approach to deploying Laravel 4
applications. It’s simply a process I’ve found works for me.
Dependencies
Our deployment processes will need to handle JavaScript and CSS files. Assetic is an asset
management library which we will use to do all the heavy lifting in this area.
To install it; we need to add two requirements to our composer.json file:
1 "kriswallsmith/assetic" : "1.2.*@dev",
2 "toopay/assetic-minifier" : "dev-master"
.
This was extracted from composer.json.
Lastly, we will also be using Jason Lewis’ Resource Watcher library, which integrates with Laravel
4’s Filesystem classes to enable notification of file changes. You’ll see why that’s useful in a bit…