I had an idea that sprang from a need: a website that would have all the local ultimate frisbee games. It would display them by type and tell me when new games were coming up. And it would have a mailing list that would email me with the games coming up for the week. There is something to this idea...
Over the weekend, I created my first package using Laravel 4.
No more bundles
Laravel 4 just came out at the end of May 2013. When it did, L3 users noticed quickly that bundles were long gone. Replacing bundles are packages. Are packages better? I have idea. I do know that they can be distributed via packagist and composer. Maybe that is why they made the switch. But really, it is all the same to me since I never really got much into L3.
Why build a package at all?
Good question. Packages are a way to add functionality to an application. But really, they are more than that. A package can have its own config files, models, views, controllers, routes, et cetera. So really, a package can be an app all by itself. HMVC, anyone?
I have a few web apps that I wrote in Codeigniter that I wanted to redo in a more cohesive way. So I created a L4 web app that I intelligently named Portal. Portal is a parent app to the other apps that I want to recode. The apps are distinct enough that they need their own configs and controllers but are related enough that it sort of makes sense to put them under the same umbrella.