charlie
Would it be hard to move a complete Filament project to Multi-tenancy ?
Thanks to all of you.
After a lot of thinking, I think I will go this way for now:
- Each Company will have a separate install (1 subdomain, 1 database, 1 Laravel install)
- On the main domain, i will install breeze, cashier, and try to make something simple
- A scheduled task on main domain will post to a very minimal API in each subdomain if the subscription for that subdomain is ok or not.
- Finally a simple middleware in each subdomain will check this status
I prefer to have this separation to avoid a lot of concerns like security risks, database size, plugins compat, etc.
The day I'll have more than 10 clients on this project, I will think about tenancy again.
Let me know if you think that's a terrible solution 🙂
8 replies
Would it be hard to move a complete Filament project to Multi-tenancy ?
To be even more clear:
The idea here would be:
- a simple one-to-many tenancy (Users 1,2,3 belongs to Company 1 ; Users 4,5,6 belongs to Company 2)
- if Company 1 subscription is up to date, then the Users 1, 2, and 3 will be able to use admin panel.
It's so simple (at least in my mind) than I wonder if I really need multi tenancy. Although it seems I need it to use any billing system
8 replies
Navigation for multi role panel
See here how it's handled in Filament resources:
https://filamentphp.com/docs/3.x/panels/resources/getting-started#authorization
10 replies
How to use Alpine in Filament?
Yeah, I did it!!!
https://filament-theme-generator.charlie-etienne.fr/
Not even one server request!
I don't know if it follows the best Alpine practices, but I manage to make it work and it's FAST
Thanks to both of you @Leandro Ferreira and @ralphjsmit
26 replies