stancl/tenancy-docs
1
0
Fork 0
mirror of https://github.com/stancl/tenancy-docs.git synced 2025-12-12 10:14:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update multi-database-tenancy.blade.md

Browse source
This commit is contained in:
Samuel Stancl 2020-07-26 22:30:07 +02:00 • committed by GitHub
parent 00f916ad7a
commit c3bda8543a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 17 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

18
source/docs/v3/multi-database-tenancy.blade.md
View file

@ -6,4 +6,20 @@ section: content
# Multi-database tenancy {#multi-database-tenancy} # Multi-database tenancy {#multi-database-tenancy}
TODO The package comes with all the tooling necessary for multi-database tenancy.
## TenantDatabaseManagers {#tenantdatabasemanagers}
TenantDatabaseManagers are classes which manage tenant databases — they primarily take care of creating and deleting them.
There are database managers for all Laravel-supported DB drivers (MySQL, PostgreSQL, SQLite). There's also a database manager for using a single database, but multiple schemas (one per tenant) with PostgreSQL.
See the `database` section of the tenancy config for more details.
## Commands {#commands}
There are also commands for working with tenant databases. Namely, `tenants:migrate` and `tenants:seed`. See the [console commands page]({{ $page->link('console-commands') }}) of the documentation.
## Jobs & Listeners {#jobs-listeners}
By default, when a tenant is created, there's also a database created for him. This is done using a JobPipeline listener in the `TenancyServiceProvider`. See the [event system page]({{ $page->link('event-system') }}) of the documentation.