Laravel 11: Multi-Tenancy with Multiple Databases

preview_player
Показать описание
We upgraded the course on multi-tenancy to Laravel 11. Let's see how to set up multiple databases for it, with stancl/tenancy package.

- - - - -
Support the channel by checking out my products:

- - - - -
Other places to follow:
Рекомендации по теме
Комментарии
Автор

Video quality has been top notch ever since you got the machine. May God continue blessing you Povilas.

brianochieng
Автор

I am using this package for a pretty large project. It works really great!

pokeripper
Автор

I can't tell you how much this video helped me. Thank you very much.

FernandoMartinsdk
Автор

Thanks for this video. You didn't discuss what changes if you're using it with an API, like a Vue SPA, with the package. Also, what's the best way to identify a tenant? Should you send the subdomain with every request, or is there another recommended approach?

If you can provide some explanation, I'd appreciate it.

learnwithshadyar
Автор

Would be interested to see how Filament v3 Panels integrate with stancl/tenancy

RuelLuna
Автор

tenant get and post route name not defined error but resource route name working how to solved it

DibakarKhamrui
Автор

Hi, Great tutorial. I've used Tenancy with Multi Tenant & single DB. I need a functionality to ghost login my admin as a tenant user. Could you help me out with that please, if possible.

jainsiddharth
Автор

I think one huge aspect of having 1 shared database that you've missed is performance, it means a single tenant with a million records would slow down database reads and queries for all tenants? I guess indexes on the tenant_id in there where claus would help with that but I still imagine they'd be performance implications?

streakifyapp
Автор

Once upon a time I've tried to do that on my own & after trying for couple of weeks, I found myself nowhere near that project 🙃 It felt too complicated

junior-dino
Автор

i tested few packages, end up multi database setting with tedious auth implementation between login from landlord and tenant.

cfufvfg
Автор

I really tried to use that package but I hate the fact he makes the tenant database migrations in a separate folder instead of the main one.

Also the routes separation for tenant and central database.

In my own implementation the application is identical for all tenants, there is no main database, or if it is, it just has some extra authorization logic to make sure it's the admin tenant, very straightforward.

My plan is to simply have another laravel instance to manage the tenants, I don't want to have all this risks of separate implementations for tenants vs central application. All my routes, everything is identical. I just have some middleware and providers that switch context for them, that's it.

manux
Автор

Hello, can you please make a video about Filament 3: Multi Tenancy File Upload? Thanks.

dennishalili
Автор

Nice one, but my concern is on jobs and queue, will they not be affected by having different databases. What are the effects of using multiple databases ? Does it limit the any functionalities in laravel ?

s.joseph
Автор

Hello, Could you make me tutorial multi tenancy and multi database in filament and laravel 11?

MinKhant-xl
Автор

Is it just me? or does the documentation on stancl/tenancy package seem to be a little bit all over the place?

getupkid
Автор

How does multiple domains affect generating urls in the app, for example, i would usually set an APP_URL to my site's domain in my .env which is useful for generating urls in tthe app, how does multi tenancy in this case affect it or url generations with route or url helper functions?

discoverlance
Автор

What happenes if central domain and tenants have separate user tables?

HossainMdAwlad
Автор

Is it possible to setup multi tenancy without assigning domains to each tenant? I suppose not but that's always a concern for me but i haven't really dived into it to get more details just yet.

discoverlance
Автор

Nice 👍 Things are all nice and dandy until you have the first tenants uploading millions of products where every pack of 5, 10, 20, 50, 100, 500 is a separate SKU and you're like uh ... that table had 20 million records last year, now its 700 million etc 😂

nimmneun