Hard to integrate to existing projects

[nikklass]

Nice work you doing. The only problem i have with this api template is that it doesnt use laravel's standard folders and structure thus making it really hard to integrate. Laravel users are already accustomed to the laravel project folder and file locations. This app requires a lot of fiddling and restructuring of the default laravel project to greater finer details, which to me, i dont think is necessary.

[pmccarren]

Hey @nikklass! Hopefully you don't mind me chiming in here!

I've built dozens of Laravel backed applications for both clients and personal ventures. Back when I was using Laravel for both the front and back-end, I would agree with you. However, I have since made a habit of splitting the UI away from Laravel and into it's own project (React/Vue backed). This lead me to using Laravel specifically for API dev, and where I think this project is targeted -- API specific projects. In my opinion the folder structure greatly aids in the design and maintenance of an API as it forces you to separate your concenrs and keep familes of code together. This is a great resource that will explain more of the intricate nuances of this specific project: http://esbenp.github.io/2016/04/11/modern-rest-api-laravel-part-1/ (authored by the same author as Larapi)

I recon if you're only building an API, then this project should help you but if you're in need to handle the UI as well then perhaps there might be another project that would be easier to work with?

With that said, I don't want to discourage you from using Larapi!

Happy to help in any way I can! Cheers!

[nikklass]

No problem. Was just an observation I made. Thanks.

[unionolivia]

@pmccarren Hi! Good to know you enjoy using larapi. How can I use larapi with laravel 5.7?

I'd be glad for your kind assistance.