DO NOT USE YET, PACKAGE IN DEVELOPMENT
This package provides a lightweight solution for making a Laravel app tenant aware. It can determine which tenant should be the current tenant for the request. It also allows you to define what should happen when switching the current tenant to another one.
It works for multitenancy projects that need to use one or multiple databases.
Before starting with the package, we highly recommend first watching this talk by Tom Schlick on multitenancy strategies.
The package contains a lot of niceties such as making queued jobs tenant aware, migrating all tenant databases in one go, an easy way to set a connection on a model, and much more.
We invest a lot of resources into creating best in class open source packages. You can support us by buying one of our paid products.
We highly appreciate you sending us a postcard from your hometown, mentioning which of our package(s) you are using. You'll find our address on our contact page. We publish all received postcards on our virtual postcard wall.
You can find the entire documentation for this package on our documentation site.
composer testPlease see CHANGELOG for more information on what has changed recently.
Please see CONTRIBUTING for details.
If you discover any security related issues, please email freek@spatie.be instead of using the issue tracker.
The code of this package is based on the code shown in the Multitenancy in Laravel series by Mohamed Said
This package aims to be a lightweight solution to make your app multitenancy aware. If you need more features, take a look at hyn/multi-tenant.
Another option you could look at it is stancl/tenancy.
The MIT License (MIT). Please see License File for more information.