Replies: 3 comments
-
IMHO, I think you're heading the right way using packages to reuse the business logic. You can also implement those 20 apps using one Laravel repo though, create one API routes and multiple other routes for each subdomain (which reuse Kernal, API routes, etc.) if that makes sense. |
Beta Was this translation helpful? Give feedback.
-
@s-patompong , thank you for the suggestion. Unfortunately it's not possible to have all of them being in one git repo. Based on some organizational policies, we need to use different git repos. But those git repos CAN use a central infra repo. |
Beta Was this translation helpful? Give feedback.
-
You can use a modular structure for that purpose. We've applied in Akaunting via our laravel-module package and it works like a charm. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I want to create these applications using laravel:
Let's say I have 20 apps in mind to create.
All of these apps have these common features:
composer.json
As you can see, while my applications are similar, I have to repeat myself a lot.
What I want is to centralize all of the common aspects ACROSS many applications.
In simple English terms, I want to have a laravel project that is called
HandyShop
and when I open it in VS Code, I don't want to seecors.php
and `middleware folder and ...I want to tell laravel hey laravel, please read all of these common features from this base package.
I have managed to centralize logic using packages. For example, I have payment package, ticketing package, etc. But I also want to centralize infrastructure.
Please guide me on how can I start? How can I do this?
Beta Was this translation helpful? Give feedback.
All reactions