multi tenancy with Filament V3 & stancl/tenancy package?
How does the current multi tenancy / context which is baked into V3 work alongside the stancl/tenancy package?
Admin panel will be with filament (for admin actions), but regular user functionality is outside the /admin route and is using stancl/tenancy at the moment for achieving multi tenancy.
How to handle this approach of using filament V3 for admin (managing settings etc) while the user application continues to use stancl/tenancy?
My mind is fixated on using only one - either filament V3 or Stancl/tenancy - to handle the full multi tenant application, but I also want to take advantage of the rapid development with Filament & the 'nice'ities / features of stancl/tenancy package.
What is the easiest way of going ahead with here? Please suggest.
6 Replies
hey, did u make any progress with this?
Oh no. We had to drop filament because it was not approved to be used for a production setup by the management 😦
Gist
Tenancy for Laravel & Filament V3 (Tenant per database)
Tenancy for Laravel & Filament V3 (Tenant per database) - BaseResource.php
yeah, but how to manage assets per tenant without that option?
should I change all my
asset() to tenant_asset?
then what about uploaded files?
we have to fix this in filament side