I'm writing an eBook called Implementing Laravel. It will be for bridging the gap between knowing how to use Laravel and knowing how to implement Laravel using SOLID principles in practices.
Queues are a great way to take some task out of the user-flow and put them in the background. Here's (most of) how I set up Beanstalkd to work with Laravel 4 in a production environment.
There has been some confusion about how to extend the Illuminate Request and/or the Response classes. Because of their importance in handling HTTP requests, these two classes are handled slightly differently than normal classes. I will go over how to extend them and then I will show you a method which favors composition over inheritance.
When your Laravel web app is behind a load balancer, reverse-proxy or other intermediary, you don't get the correct user IP address reported to you. This will cover how to retrieve the correct client IP address in those situations.
Facades are great for making your packages easy to use by other developers. Learn how to create and implement your own Facades.
This will review solving the "Lost Update" problem with ETags within a Laravel 4 RESTful API. This builds off of previous ETag related articles.
There are a few guides out there which help you install Laravel 4 in a way that let you pull in updates to the skeleton app in addition to the composer-based libraries. I think this is the best, quickest way.
In looking to build a RESTful API, an important consideration is how to handle errors. Most errors are displayed to users in HTML, as these are web applications. However, API's need some special care.
Here's how to get started really quickly with Laravel 4. Updated since Laravel 4's official release!