- Laravel: 5.3 & 5.4
- Author: Ollie Read
- Author Homepage: http://ollieread.com
Laravel package for multitenancy using subdomain and/or domain based identification. The package itself works much in the same way as the default Auth library.
Firstly you want to include this package in your composer.json file.
"require": {
"ollieread/laravel-multitenancy": "^2"
}
Now you'll want to update or install via composer.
composer update
Next you open up app/config/app.php and add the following.
Ollieread\Multitenancy\ServiceProvider::class,
Then the facade.
'Multitenancy' => Ollieread\Multitenancy\Facades\Multitenancy::class,
Finally, run the following command to publish the config.
php artisan vendor:publish --provider=Ollieread\Multitenancy\ServiceProvider
There are three main parts to the configuration.
#####The provider
'provider' => 'eloquent',
By default this is can be either eloquent or database. If you add a custom provider, you'd use the name here.
#####The domain
'domain' => env('MULTITENANCY_DOMAIN', 'mydomain.com'),
The domain that should be used for tenant based subdomains.
#####The Provider settings
'eloquent' => [
// The model representing a tenant
'model' => Ollieread\Multitenancy\Models\Tenant::class
],
'database' => [
// The table where tenants are stored
'table' => 'tenants',
// The foreign key for identifying tenant ownership
'foreign_key' => 'tenant_id',
// The identifiers used to identify a tenant
'identifiers' => [
'slug', 'domain'
]
]
These particular settings are defined by the individual providers and the defaults contain small descriptions.
Access the currently identified tenant by using Multitenancy::tenant().
There is a method for create route groups that should be part of the tenant system.
Multitenancy::routes(function (Router $router) {
$router->get('/tenancy', function() {
$tenant = Multitenancy::tenant();
dd($tenant);
});
});
It is worth noting that if this method is called inside a group that has the default web group, it'll error. You should instead wrap the web group routes in this, eg:
protected function mapWebRoutes()
{
Multitenancy::routes(function (Router $router) {
Route::middleware('web')
->namespace($this->namespace)
->group(base_path('routes/web.php'));
});
}
If you wish to use your own route groups, just make sure you load the following middleware before any authentication related middleware.
Ollieread\Multitenancy\Middleware\LoadTenant
To generate a url for a tenant based route, you can use the following methods:
Multitenancy::route($name, $paramaters = [], $absolute = false);
Multitenancy::url($path, $paramaters = [], $secure = false);
These methods act the same as route() and url() except that they automatically add the correct domain for the current tenant.
NOTE: The url() method has been removed for now as it wasn't working exactly as intended.
If using the eloquent provider, the specified model must implement:
Ollieread\Multitenancy\Contracts\Tenant
There is a trait available that provides implementation using the default column names slug and domain. It also offers access to route() and url() on the model. This trait is:
Ollieread\Multitenancy\Traits\Tenant
There is a scope available to you for use on models that belong to a tenant. To use this, add the following trait to the models you wish to belong to a tenant:
Ollieread\Multitenancy\Traits\TenantOwned
This only works for models that have the tenant foreign key as a column, and is designed to prevent you from having to manually add where clauses everywhere.
If you wish to see all entries regardless of the current tenant, use the withAll() method.
If you wish to use a multi database multitenant approach (each tenant has their own database), you can do so with this package.
Create yourself a base configuration within the database configuration file. For example, duplicate the mysql connection information, rename to whatever you would like, set the database name to be an empty string, and then update the multidatabase.connection setting in the multitenancy configuration file.
By default, the connection will look for a database named tenant_{id} where {id} is the id of the row from the tenant model. To override this, you need to provide a configuration parser, which will allow you to adjust all of the connection configuration settings per tenant. Below is how to do so, using the default implementation.
Multitenancy::setConnectionParser(function ($config = [], Tenant $tenant) {
$config['database'] = 'tenant_'.$tenant->id;
return $config;
});
To use this, simple reference the multitenancy connection either in the Eloquent model property, or by using DB::connection('multitenancy') when using the base database library.
If you're using the TenantOwned trait on your user model you won't need to do anything with the Eloquent provider.
For session based authentication you'll want to use the session.multi guard, which is identical to the default session guard, except that prefixes session and cookie names with the tenant primary identifier to allow users to be logged into multiple tenants at once.
If you're using the Database provider for auth, you'll want to use the database.multi provider so that you only retrieve records specific to the current tenant.
This package supports custom providers. To create a custom provider, create a class that implements Ollieread\Multitenancy\Contracts\Provider and then register it like so:
Multitenancy::extend('eloquent', function ($app, $config) {
return new Eloquent($config['model']);
})->extend('database', function ($app, $config) {
return new Database($app['db']->connection(), $config['table'], $config['identifiers']);
});
The method is setup for daisy chaining should you need to add multiple.