Everything from authentication till data fetching and storing will have to run through a seperate DB connection,
You can override whatever you want. Question is are you willing to ?
Hi guys, i would like to get your idea's on the following scenario.
I have an existing website which is totally custom, no framework, no proper database conventions etc. but with quite a bit of data in it (leads, appointments, projects, finance, products etc.), whilst i'm still trying to convince the owner to remake it in Laravel, in the meantime i have to create a new addition to this site.
The goal is to create a responsive page for advisors (which will use 4G iPads) to insert data directly from the customers home into the system. In all my enthousiasm i grabbed a fresh Laravel installation, installed all the packages i'll be needing, and started working on a master page, when suddenly i realised i won't be able to use any laravel database tables.
Everything from authentication till data fetching and storing will have to run through a seperate DB connection, so my question to you guys is, is it wise to create it in Laravel (keeping in mind the fact that in the future the customer might want to switch to Laravel anyway), or should i append it to the already existing system.
Please or to participate in this conversation.