mirror of
https://github.com/stancl/tenancy-docs.git
synced 2025-12-15 03:34:03 +00:00
fix: checks for mispelled words
This commit is contained in:
parent
ecf4391f94
commit
e6494c7a15
5 changed files with 5 additions and 5 deletions
|
|
@ -4,7 +4,7 @@ extends: _layouts.documentation
|
|||
section: content
|
||||
---
|
||||
|
||||
# Cached lookup {cached-lookup}
|
||||
# Cached lookup {#cached-lookup}
|
||||
|
||||
If you're using multiple databases, you may want to avoid making a query to the central database on **each tenant request** — for tenant identification. Even though the queries are very simple, the app has to establish a connection with the central database which is expensive.
|
||||
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ If you wish to use autoincrement ids instead of uuids:
|
|||
1. set this config key to null, or create a custom tenant model that doesn't use this trait
|
||||
2. update the `tenants` table migration to use an incrementing column type instead of `string`
|
||||
|
||||
### Domain model {3domain-model}
|
||||
### Domain model {#domain-model}
|
||||
|
||||
`tenancy.domain_model`
|
||||
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ If your command's signature were `email:send {--queue} {--subject=} {body}`, yo
|
|||
php artisan tenants:run email:send --tenants=8075a580-1cb8-11e9-8822-49c5d8f8ff23 --option="queue=1" --option="subject=New Feature" --argument="body=We have launched a new feature. ..."
|
||||
```
|
||||
|
||||
## **Tenant list** {#teant-list}
|
||||
## **Tenant list** {#tenant-list}
|
||||
|
||||
```
|
||||
php artisan tenants:list
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ Note that you can register listeners to this package's events **anywhere you wan
|
|||
Event::listen(TenancyInitialized::class, BootstrapTenancy::class);
|
||||
```
|
||||
|
||||
# Bootstrapping tenancy [#bootstrapping-tenancy]
|
||||
# Bootstrapping tenancy {#bootstrapping-tenancy}
|
||||
|
||||
By default, the `BootstrapTenancy` class is listening to the `TenancyInitialized` event (exactly as you can see in the example above). That listener will execute the configured tenancy bootstrappers to transition the application into the tenant's context. You can read more about this on the [tenancy bootstrappers]({{ $page->link('tenancy-bootstrappers') }}) page.
|
||||
|
||||
|
|
|
|||
|
|
@ -49,7 +49,7 @@ You can read more about this on the *Queues* page:
|
|||
|
||||
[Queues]({{ $page->link('queues') }})
|
||||
|
||||
## Redis tenancy bootstrapper {#resis-tenancy-bootstrapper}
|
||||
## Redis tenancy bootstrapper {#redis-tenancy-bootstrapper}
|
||||
|
||||
If you're using `Redis` calls (not cache calls, **direct** Redis calls) inside the tenant app, you will want to scope Redis data too. To do this, use this bootstrapper. It changes the Redis prefix for each tenant.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue