I am currently building an Invoice System with Laravel. I am just wondering how you would go about this.
Would you split your Application into "modules / packages"?
For example you would make a package for the Invoices, for the Ticket System and so on?
I think the benefit would be that i can just update/maintain my packages separately without touching my whole Application, or am i wrong? :)
Or would you build the complete Application just right out of the box without your own packages?
If its something I can reuse on other projects, a package 100%. I like to keep my controllers thin, and my models for database transactions, if its outside of those two then I typically put it in a package and register it with the container.
Hi there, I am working in a quotes system, maybe the samely case, and I am creating my own package to the main tasks. In this way you can use it in further projects. I see it in that way.
Samuel Oloruntoba
Java is to JavaScript what Car is to Carpet.
When working with Laravel, I create each major feature as a package. I think this gives me a form of modularity. I still use git to track each package and then use composer to manage my dependencies(both public and private).