You are viewing the documentation for an older version of this package. You can check the version you are using with the following command:

composer show spatie/laravel-multitenancy

Using multiple databases

On this page

  1. Configuring the database connections

Before using the following instructions, make sure you have performed the base installation steps first.

Only use the instructions on this page if you want each of your tenants to have their own database.

When using a separate database for each tenant, your Laravel app needs two database connections. One named landlord, which points to the database that should contain the tenants table and other system-wide related info. The other connection, named tenant, points to the database of the tenant that is considered the current tenant for a request.

In the multitenancy config file, you must set a name in tenant_database_connection_name. You can use tenant, but it could be any name that you want. The landlord_database_connection_name must also be set. A logical value could be landlord, but again, you could use any name you want.

Next, let's create the connections themselves. In the database config file, in the connections key, you must add a database configuration for the tenant and landlord connections.

In the example below, the mysql driver is used, but you can use any driver you'd like. For the tenant connection, you should set database to null. The package will dynamically set the database name depending on the tenant that's considered the current one.

// in config/database.php

'connections' => [
    'tenant' => [
        'driver' => 'mysql',
        'database' => null,
        // other options such as host, username, password, ...
    ],

    'landlord' => [
        'driver' => 'mysql',
        'database' => 'name_of_landlord_db',
        // other options such as host, username, password, ...
    ],

With the database connection set up, we can migrate the landlord database.

First, you must publish the migration file:

php artisan vendor:publish --provider="Spatie\Multitenancy\MultitenancyServiceProvider" --tag="migrations"

The command above will publish a migration in database/migrations/landlord that will create the tenants table.

Perform this command to run that migration. The value of the database option should be the landlord database connection name.

php artisan migrate --path=database/migrations/landlord --database=landlord

When creating new migrations that should be performed on the landlord database, you should store them in the database/migrations/landlord path. After creating your own migrations, use the command above to migrate the landlord database.

When making a tenant the "current" one, the package will execute all tasks that are specified in the switch_tenant_tasks key of the multitenancy config file.

The package ships with a task called SwitchTenantDatabase that will make the tenant database connection use the database whose name is in the database attribute of the tenant.

You should add this task to the switch_tenant_tasks key.

/*
 * These tasks will be performed to make a tenant current.
 *
 * A valid task is any class that implements Spatie\Multitenancy\Tasks\SwitchTenantTask
 */
'switch_tenant_tasks' => [
    Spatie\Multitenancy\Tasks\SwitchTenantDatabaseTask::class,
],

The package also provides other tasks that you could optionally add to switch_tenant_tasks. You can also create a custom task.

Now that automatic database switching for tenants is configured, you can migrate the tenant databases. Because there are so many ways to go about it, the package does not handle creating databases. You should take care of creating new tenant databases in your own application code. A nice place to trigger this could be when a Tenant model gets created.

If you want to get a feel of how the package works, you could create a couple of rows in the tenants table, fill the database attribute and manually create those databases.

When you want to migrate tenant databases, all future migrations should be stored in database/migrations.

To perform these migrations, you can use the tenants:migrate command. This command will loop over all rows in the tenants table. It will make each tenant the current one, and migrate the database.

php artisan tenants:artisan "migrate --database=tenant"

If you want to have dedicated directory for tenant migrations (database/migrations/tenant) you can simply run:

php artisan tenants:artisan "migrate --path=database/migrations/tenant --database=tenant"

If you also want to seed tenant database you can execute this command:

php artisan tenants:artisan "migrate --database=tenant --seed"

This will cause all seeders to run. In your DatabaseSeeder you can use Tenant::checkCurrent() to verify if the seeding is done for a tenant or a landlord.

use Illuminate\Database\Seeder;
use Spatie\Multitenancy\Models\Tenant;

class DatabaseSeeder extends Seeder
{
    public function run()
    {
        Tenant::checkCurrent()
           ? $this->runTenantSpecificSeeders()
           : $this->runLandlordSpecificSeeders();
    }

    public function runTenantSpecificSeeders()
    {
        // run tenant specific seeders
    }

    public function runLandlordSpecificSeeders()
    {
        // run landlord specific seeders
    }
}

All models in your project should either use the UsesLandlordConnection or UsesTenantConnection, depending on if the underlying table of the models lives in the landlord or tenant database.

When using multiple tenants, you probably want to isolate the cache or use separate filesystems per tenant, ... These things are performed by task classes that will be executed when making a tenant the current one.

Using a single database
Determining the current tenant
Help us improve this page