Question 1

How to set up Tenanti for separate databases per tenant?

Accepted Answer

Configure the driver with `shared` set to false in `tenanti.php`, then add a connection resolver in a service provider to dynamically set the database name based on tenant ID, as detailed in the multi-database section.

Question 2

Tenanti vs Spatie Laravel Multitenancy?

Accepted Answer

Tenanti focuses on database schema management and migrations with native Laravel integration, while Spatie's package offers broader tenant isolation features including filesystem and cache. Choose Tenanti for deep database control, Spatie for a more comprehensive solution.

Question 3

Does Tenanti support queueing migrations for new tenants?

Accepted Answer

Yes, it includes a `tenanti:queue` command that allows migration actions to be executed via Laravel's queue system, minimizing performance impact during tenant setup, as mentioned in the console support.

Question 4

How to handle tenant-specific database connections dynamically?

Accepted Answer

Use the connection resolver in a service provider by calling `Tenanti::connection()` with a callback that modifies the config based on the tenant entity, as shown in the multi-database setup example.

Question 5

Can Tenanti be used with Laravel Nova or other admin panels?

Accepted Answer

It can be integrated, but requires additional setup to manage tenant contexts in the admin panel, as Tenanti doesn't provide built-in UI components and focuses on backend database management.

Question 6

What are the performance implications of using Tenanti with many tenants?

Accepted Answer

Performance depends on configuration; using separate databases can scale well but requires more resources, while shared databases with schema isolation might face contention. Queue integration helps mitigate migration overhead.

Tenanti

What is Tenanti?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions