recommendation transforming full php app to filamentphp
hi i got a system that is made full in php (i dont have source code) i would like to create from scratch the system using filamentphp so i got full control on code. Currently system have two path /admin /client, should i use just one panel in filament and use shield? or should i create multiple panels. In addition i got a users question, i got all users data in a table but with a non encrypted password (thats how current system works sadly) i can reutilize the same table in filament?also i got another table for admin users, i know password will need to change or by encrypted, i can manage a new field i think.
Currently system have two path /admin /client, should i use just one panel in filament and use shield?
Recently I did a project migration from Laravel custom dashboard to filamentphp.
I suggest you use the separate (two) panels to redirect them to the different panels easily.
i can reutilize the same table in filament?also i got another table for admin users, i know password will need to change or by encrypted, i can manage a new field i think.
I recommend you to hash the password instead of maintaining in the plain text.
@tisuchi and what about if i have my clients in one table and my regular admin users in another? should i use only one login table and have a client_Detail table linked to a primary key to get all details from client-? as client have like 30 custom fields
