You might find something interesting here.
This is an amazing list, with a section on example applications;
I know this post is a few months old -- but it comes up in search results.
Was working with a local deployment of Pulled Over for a different call recording purpose, and was learning a bit from the code. (site is https://pulledover.us/ )
Anyway, code is https://github.com/mattstauffer/pulledover and it seemed like a good and simple but also diverse/real example (with tests) worth noting in 5.2.
I'm the developer of Invoice Ninja, I thought it might be helpful to share some thoughts.
First off... I agree, I wouldn't suggest using Invoice Ninja as a model for how to write your Laravel app.
The app was started over three years ago with Laravel 4. While we've tried to keep somewhat up to date (we're currently at 5.2) we haven't been able to rewrite all of our old code/features using the new features of the framework.
Besides that, the controllers definitely do far too much (and other things...). This is in large part due to focusing more of my time on adding more features and less on refactoring code. Another important factor however is simply not fully understanding the problem domain before creating the app. I'm not sure I had even created an invoice before :)
That said, if you need an invoicing app I couldn't recommend it more strongly. We've been able to leverage our open source community along with our large hosted user base to constantly monitor and improve our app to provide a rock solid program.
Defining our constants in the routes file may not be conventional but it isn't creating a lot of bugs either. Although the controllers are too thick there's isn't much code duplication, just code that belongs elsewhere. And while there's some bad there's also some stuff that we got right, such as our use of presenters, form requests, policies, transformers and events.
If I were to start over there's a lot I'd change but there's also a lot I'd keep the same. We have over 20,000 users running our software, we can say with great confidence that it works well. We're constantly working to refactor our code, hopefully we'll be able to improve it more over time.
Please or to participate in this conversation.