Answer the question
In order to leave comments, you need to log in
Why vue in laravel, if you can separately?
Why use vue in laravel when you can do it separately? For example, we make the front just on vue, which lies on the computer and builds, after which it is uploaded to the server, for example, to the APP folder. And next to it, for example, there is a folder where laravel lies and, for example, is called API. As a result, it is more convenient for developers from the front to make their own front and upload it simply to the APP folder, and do the backends in their own folder (API). All this business is connected by usual requests. This is more convenient, as it seems to me at first glance, than making a front in laravel, where components are obtained and everything else is stored on the server and is a little structurally not so scattered? If different people are working on the back and front, I think the first option is more convenient, isn't it? In that sense, even if everything is on the server and two frontends are working, which are simultaneously finalizing something. In the first version, you did it yourself, pulled up from the git what another developer did. Collected all this business and filled in on serv. Please explain?
Answer the question
In order to leave comments, you need to log in
As long as you are driving small data through the API, you can do any up, there are no problems.
But if you have a complex site and at one point, for example, in a piece of the Vue template you need to insert a piece of the template from the server, where the necessary data is substituted into it after the necessary processing, you will start having problems with this division: half of the work on the back, the second half at the front, too strong logical connectivity between them or too voluminous data that you have to drag into processing ... It's easier to localize everything where the logic can be collected in one place than to suffer such freedom.
If it's a small project and you're working on it alone, it's much easier not to worry and do everything in one place. But if the project starts to grow, or it was originally conceived with the participation of a whole team of developers, then the front and back are definitely separated, since it is really much more convenient.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question