recommend redis over memcache for central caching

theforeman · Mar 7, 2023 · 9863f89 · 9863f89
1 parent 297f7ad
commit 9863f89
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/_includes/manuals/3.6/5.8.4_other_considerations.md b/_includes/manuals/3.6/5.8.4_other_considerations.md
@@ -3,4 +3,4 @@ There are other considerations when creating a cluster:
 
 1. You might want to share a common hostname, which can be set during installation or by modifying your Apache config files.
 2. You might want a custom cert to reflect the cluster's cname, and you'll want to make sure your Foreman-related infrastructure is [configured to use SSL](manuals/{{page.version}}/index.html#5.4SecuringCommunicationswithSSL).
-3. You can use a central memcached instance instead of each Foreman instance's local cache. Foreman has a [plugin](https://github.com/theforeman/foreman_memcache) you can use.
+3. You can use a central Redis instance instead of each Foreman instance's local cache.
diff --git a/_includes/manuals/nightly/5.8.4_other_considerations.md b/_includes/manuals/nightly/5.8.4_other_considerations.md
@@ -3,4 +3,4 @@ There are other considerations when creating a cluster:
 
 1. You might want to share a common hostname, which can be set during installation or by modifying your Apache config files.
 2. You might want a custom cert to reflect the cluster's cname, and you'll want to make sure your Foreman-related infrastructure is [configured to use SSL](manuals/{{page.version}}/index.html#5.4SecuringCommunicationswithSSL).
-3. You can use a central memcached instance instead of each Foreman instance's local cache. Foreman has a [plugin](https://github.com/theforeman/foreman_memcache) you can use.
+3. You can use a central Redis instance instead of each Foreman instance's local cache.