GitBook: [#8] No subject

advanced-usage/caching.md

@@ -4,3 +4,7 @@ Soketi has a caching layer built within. This allows you to speed up some proces
 
 Currently, the caching system is used to [cache app retrievals](../app-management/introduction.md#caching-app-retrievals) (if enabled) or store the cache for [Cached Channels](https://blog.pusher.com/introducing-cache-channels/) when scaling across multiple nodes.
 
+| Name                       | Default  | Possible values   | Description                                                                                                         |
+| -------------------------- | -------- | ----------------- | ------------------------------------------------------------------------------------------------------------------- |
+| `SOKETI_`CACHE\_DRIVER     | `memory` | `memory`, `redis` | The caching driver.                                                                                                 |
+| `CACHE_REDIS_CLUSTER_MODE` | `false`  | `false`, `true`   | Enable this if you run Redis in Cluster mode. [Read more](../getting-started/redis-configuration.md#redis-cluster). |

app-management/introduction.md

@@ -16,7 +16,9 @@ Within the following documentation pages, we will discuss how to configure apps
 
 Soketi can cache the apps that are retrieved for authentication. The apps retrieved in the cache cannot be purged until the TTL causes it to get evicted and replaced with the fresh value from the database. The caching is on a per-app basis.
 
-Please also see the caching sectio.
+{% hint style="info" %}
+Please also see the [caching section](../advanced-usage/caching.md) for additional configuration.
+{% endhint %}
 
 | Name                               | Default | Possible values     | Description                                                   |
 | ---------------------------------- | ------- | ------------------- | ------------------------------------------------------------- |