From bc9de2e0435fcd48940d9fc73a6478e72175c4f0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Samuel=20=C5=A0tancl?= Date: Thu, 4 Apr 2024 21:06:48 +0200 Subject: [PATCH] Update session-scoping.blade.md --- source/docs/v3/session-scoping.blade.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/docs/v3/session-scoping.blade.md b/source/docs/v3/session-scoping.blade.md index 6f36976..e20af26 100644 --- a/source/docs/v3/session-scoping.blade.md +++ b/source/docs/v3/session-scoping.blade.md @@ -14,6 +14,8 @@ Here's how you can prevent this. ## Storing sessions in the database {#storing-sessions-in-the-database} +> Note: This approach has more variables than Redis, making it less reliable. It's recommended to use phpredis + the Redis session driver for proper session scoping. + 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}