One setup that I use I have multiple discourse containers running behind a reverse proxy on a single server. For a time, I was using DISCOURSE_REDIS_DB: x to allow multiple Discourse servers to use a single redis server. Largely because I am lazy and don’t like keeping careful track of which server is using which number, I wanted to increase the number of redis DBs in redis to more than 16. When I asked about such, the answer I got suggested that it is a very bad idea to use redis_db to have multiple sites on a single redis. And since then I have reconfigured things to spin up a separate redis for each site (which makes them easier to keep up with since I can use a name for them). But this seems a little silly. And now that I’m looking, I see this: app/models/global_setting.rb main end end def self.get_message_bus_redis_replica_port return message_bus_redis_replica_port if message_bus_redis_replica_port.present? if respond_to?(:message_bus_redis_slave_port) && message_bus_redis_slave_port.present? message_bus_redis_slave_port end end def self.redis_config @config ||= begin c = {} c[:host] = redis_host if redis_host c[:port] = redis_port if redis_port if get_redis_replica_host && get_redis_replica_port && defined?(RailsFailover) c[:client_implementation] = RailsFailover::Redis::Client c[:custom] = { replica_host: get_redis_replica_host, So, I was wondering if it’s OK to use redis_db or whether each Discourse needs its own redis.

Each Discourse needs its own totally separate redis server because message-bus uses Redis Pub/Sub, which is shared between all databases on a Redis server. If you run Discourse in a multisite configuration, then we automatically add a site-specific prefix to all keys and pub-sub channels. That same prefixing is not available for standard ‘single site’ installations.

This seems to be a gross architectural oversight. Could you please make redis key prefixing possible in a single-site installation so we can have multiple installations of Discourse on one redis host? Unless I’m misunderstanding something, this is a very simple solution that would greatly reduce the complexity and overhead for folks that need to run more than one discourse.

דיון מרובה על שרת Redis בודד

תמיכה התקנה

pfaffman (Jay Pfaffman) 24 בפברואר,‏ 2022,‏ 10:56pm 3

Perfectly understandable. Thanks very much for your lucid explanation!

נושא		תגובות	צפיות
Expected Number of Redis Connections Self-hosting hosting	4	1083	14 במאי,‏ 2022
How to set redis DB ID in Docker container? Self-hosting	6	3450	9 ביוני,‏ 2020
Shared Redis caching Self-hosting	1	1084	15 בדצמבר,‏ 2015
Two Discourses - in containers - interfere with each other? Self-hosting unsupported-install , docker	4	651	29 באוגוסט,‏ 2023
Multiple app containers for a single Discourse site Self-hosting hosting	5	319	19 בינואר,‏ 2026

דיון מרובה על שרת Redis בודד

נושאים קשורים