georgetown74's avatar

Create Laravel Admin Panel for Existing (Non-Laravel) Web App

I have an existing web app (LAMP stack but does not use Laravel) for which I want to create a backend admin panel using Laravel. Is there a specific Laracast series, guide, or other resource that walks-through this process and discusses best practices?

0 likes
6 replies
vincent15000's avatar
Level 63

There are several presentations of admin webpanels working with Laravel, but I don't know any serie which presents any way to develop a webpanel.

What I wonder is how you will manage the entry point of the non Laravel part of the website and the entry point of the Laravel part. I think that you will need to have for example a subdomain to access to the admin webpanel because you will have two different applications (website non Laravel and webpanel Laravel).

georgetown74's avatar

@vincent15000 Thank you for the response! I have found series/guides/resources about developing admin panels with Laravel, more generally, but what is more relevant to me is exactly what you were writing about in the second part of your answer. That is, managing the "Laravel part" with the "non Laravel" part, and I am wondering if there were resources specifically about that. I think it will be fine to have two different applications, and the subdomain idea that you suggested seems like it could work (something like admin.example.com). I think the trick, then, is can the Laravel admin webapp and the non Laravel web app share access to the same database? I know that, for example, I will need to override the default table name conventions for the admin webapp because the existing database tables do not follow Laravel conventions (e.g., a "user" table rather than a "users" table; https://medium.com/@mohansharma201.ms/laravel-working-with-an-existing-database-d9eba86aa941 ). Do you know of resources that would discuss things like that?

1 like
vincent15000's avatar

@georgetown74 Sure you can share access from to the same database. In your Laravel models, you can specify the table name if it is different from the Laravel table name convention.

protected $table = "user";
georgetown74's avatar

@vincent15000 Confirmed, thank you. I also found a resource about creating a user-defined bridge network with Docker so that the Laravel app can connect to the database used by the non-Laravel app.

1 like

Please or to participate in this conversation.