Okay so I have done some digging and found that domain routing is one way to implement this, does anyone else have an alternative method if so why would you recommend it?
@amirjani have you ever built multiple frontends with laravel seperated by subdomains?
What steps have you taken so far to debug this fault?
Laravel-Permission, Laravel-Debugbar look useful. I don't use an IDE i tend to use VI or Nano via SSH straight on my dev server but thank you for the recommendation. For notifications I will keep that in mind once i start building the GUI's at this time im focusing purely on the routing and business logic. Thank You Amirjani
I am new to Laravel most of my PHP experience is self taught so i am by no way an expert.
I have been reading up on different frameworks for some time to find the best for my project and seem to always end up looking into Laravel so I think its time for me to start using it.
My project is going to require a multiple interfaces;
1 ) Frontend (Public Website)
Each interface would operate on its own sub domain.
Each Interface would require it's own strict permissions dependant on the user logging in.
Each Interface should share majority if not all models
Once built and tested for data protection compliance this core system would need to be extendable by a modular based system probably git sub module based so that users of this system can customise it to be suitable for there use as much as possible without touching code.
Please can you all discuss and give advice on how you would personally go about this for me to test to see which one works best for my project.
It is highly appreciated.