Closes #25.

structurizr · Nov 18, 2024 · 9c197a7 · 9c197a7
1 parent a163ace
commit 9c197a7
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/onpremises/07-http-sessions.md b/onpremises/07-http-sessions.md
@@ -21,6 +21,6 @@ To use Redis for HTTP session storage, assuming that you have a Redis installati
 `structurizr.properties` file, and restart your on-premises installation.
 
 1. Add a property named `structurizr.session` with a value of `redis`.
-2. Add properties named `structurizr.redis.host`, `structurizr.redis.port`, and `structurizr.redis.password` with values that reflect your Redis installation.
+2. Add properties named `structurizr.redis.host`, `structurizr.redis.port`, `structurizr.redis.database`, and `structurizr.redis.password` with values that reflect your Redis installation.
 
 A side-effect of using Redis for session storage is that user sessions should survive restarts of the on-premises installation.
diff --git a/onpremises/08-data-storage.md b/onpremises/08-data-storage.md
@@ -78,12 +78,13 @@ structurizr.cache=local
 ```
 
 And if you have multiple on-premises installation servers, you'll ideally need to use a distributed cache.
-At this time, only Redis is supported (change the Redis host/port/password as required):
+At this time, only Redis is supported (change the Redis host/port/database/password as required):
 
 ```
 structurizr.cache=redis
 structurizr.redis.host=localhost
 structurizr.redis.port=6379
+structurizr.redis.database=0
 structurizr.redis.password=
 ```