l have a website where Tutors logs in and sell there courses, then Students can buy these courses.
The requirement is to take a commission from each sale for the website owner.
Anyone have used Paypal in a similar scenario ? How a work flow like this will work when using Paypal as a payment method?
Off-topic: I hate Paypal docs soooooo much, Is there a service that give me a Paypal payment method with a good docs?
I am using https://github.com/nWidart/laravel-modules to split my app into modules. And I will be using Vue to create a SPA.
I am planning to have an Admin module ( admin dashboard ) and Front module ( front-site ). These are the entry point for the app, and each one has its own script.
For example: inside Modules/Front/Resources/Views/app.blade.php
And there is other modules like ( User - Post - Category ..etc )
I am having a hard time on how to setup something like this and how to connect vue components together. Is there some GitHub for starters to demonstrates a Mdoular approach with SPA?
Rass left a reply on How To Structure Multi Dashboards Folders And Files?
@devfrey Thanks for the info. It seems I might do it as you said.
For now, while searching.. I came a cross something called "modules", but I am having a hard time to understand how to structure this app as "modules", and if its a good idea to structure it as modules?
Rass started a new conversation How To Structure Multi Dashboards Folders And Files?
Lets say I have these dashboards:
And there is the Front site where guests can see:
Each dashboard has it own business logic. including the Front.
I was thinking of structuring it like this:
|- app/ |- Console/ |- Commands/ |- Events/ |- Exceptions/ |- Http/ |- Controllers/ |- Front/ |- Admin/ |- student/ |- teacher/ |- Middleware/ |- Jobs/ |- Listeners/ |- Providers/ |- Models |- User.php \ can be admin - student - teacher |- Lesson.php |- Article.php |- Role.php \ admin role - student role - teacher role |- Permission.php |- database/ |- factories/ |- migrations/ |- seeders |- config/ |- routes/ |- front/ |- admin/ |- student/ |- teacher/ |- resources/ |- assets/ |- front/ |- admin/ |- student/ |- teacher/ |- lang/ |- front/ |- admin/ |- student/ |- teacher/ |- views/ |- front/ |- admin/ |- student/ |- teacher/
but I don't know, since the app will be more and more bigger in the future, this seems very messy to me.
I am looking for something that can be maintainable, and when I want to change something or add some new feature I know where to look easily.
What the best practice to structure these folders and files? How will you structure something like this?