One of the most common questions we receive from other Laravel users is how to organize a large code base like Snappy. In this post I’ll share a few of the things we do to keep our Laravel code base manageable.
I just started a new side project and have been revisiting the setup described. This organization really works well and the bigger the application grows the more useful the structure is. I’ve also been involved in a few other applications that use the standard models and controllers and it can get nasty fast.
This post is about 6 months old but still as relevant as ever. Also I highly recommend checking out Taylor’s book Laravel 4: Advanced Application Architecture. It’s a short read at 67 pages but lots of great knowledge shared within.
Join the weekly newsletter and never miss out on new tips, tutorials, and more.
TLDRLegal – Software Licenses Explained in Plain English
List of software licenses in short easy to understand terms. My favorite: DBAD – Considered a “joke”…
Vagrant 1.5 Feature Preview: Vagrant Share
With Vagrant 1.5, we’re introducing a feature that will allow you to share your running Vagrant environment wit…