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

Add and fix heading IDs

Browse source
This commit is contained in:
lukinovec 2023-01-06 07:49:24 +01:00
parent 8029bdc51c
commit e7edb9331b
11 changed files with 17 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

4
source/docs/v3/session-scoping.blade.md
View file

@ -16,7 +16,7 @@ Here's how you can prevent this.
Since the databases are automatically separated, simply using the database as the session driver will make this problem disappear altogether.
## Storing sessions in Redis {storing-sessions-in-redis}
## Storing sessions in Redis {#storing-sessions-in-redis}
This is the same solution as using the DB session driver. If you use the [`RedisTenancyBootstrapper`]({{ $page->link('tenancy-bootstrappers') }}), your Redis databases will be automatically separated for your tenants, and as such, any sessions stored in those Redis databases will be scoped correctly.
@ -24,4 +24,4 @@ This is the same solution as using the DB session driver. If you use the [`Redis
Alternatively, you may use the `Stancl\Tenancy\Middleware\ScopeSessions` middleware on your tenant routes to make sure that any attempts to manipulate the session will result in a 403 unauthorized response.
This will work with all storage drivers, **but only assuming you use a domain per tenant.** If you use path identification, you **need** to store sessions in the database (if using multi-DB tenancy), or you need to use single-DB tenancy (which is probably more common with path identification).
This will work with all storage drivers, **but only assuming you use a domain per tenant.** If you use path identification, you **need** to store sessions in the database (if using multi-DB tenancy), or you need to use single-DB tenancy (which is probably more common with path identification).