Answer the question
In order to leave comments, you need to log in
How to organize code reuse in two Laravel projects?
The task is to write a backend for a site that works in two different countries. 90% of them are identical, but 10% are some regional specifics. Now the backends work as two independent repositories (one fork of the other). There is no code reuse, and they spread farther and farther apart, or you have to do double work each time to roll out the same functionality.
I don’t want to fall from one hole to another in the process of rewriting, so I ask for advice on how best to organize code reuse, while maintaining the overall architecture and rules, but leaving room for local maneuvers.
Several options come to mind:
Answer the question
In order to leave comments, you need to log in
With other unknowns, I think the optimal is usually
One repository - two servers. There is some customization with configs, but in general the same;
No one will advise you anything, because no one has before their eyes what you have. The choice is yours to make based on your experience with the project.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question