Multi-Tenancy in Filament 3: Practical Demo

This appears to be a same database multi-tenancy. Honestly I find it overkill for Filament to touch on multi-tenancy and in my view should let a multi-tenancy package like spatie handles it.

Please make a video on multi-tenancy + filament shield

what up with the filament daily channel?

Do you have or can suggest some FIlament Tenancy users and permissions management package?

foreignId vs foreignIdFor what would u prefer? my opinion "For" version better bec add more sustainable code like enums. (And class is clickable what is Huge adv.)

This applycompanyscopes middleware doesnt work if you use the DB facade, like DB::table for a widget query for example

I love the way you explain things.. you're so clear... Awesome.

You choose filament or flux 🤔

that's great,Very Helpful!.

Thanks

I think this is the laziest way to do multi-tenancy. I've never liked this single-database concept. It's very, very risky.

At least multiple-databases, and for more advanced scenario, go to containers or more separation, of course, depends on use case and everything else.

Can i use tenancy multiple db with modules? Especially to run the migration for tenant x and module y

Since I am only focusing on Backend, provide API.

How to apply that middleware if not using filament? I can't apply it globally for Model since the Model can be access from Admin too.

Could add the model global scope to an abstract layer, yeah?

can it be used for, multi branches instead of companies? Or there is another tweak to it? @LaravelDaily

Thanks for the awesome video! I also watched the “Multiple Panels in Filament 3” one. Quick question: If we’re building multiple panels—one for central admin to manage tenants (like registering or deleting them) and another for tenant admins to manage their own models—do we need to turn on “teams” in Spatie roles/permissions, in addition to setting up “multi-tenancy” in Filament?