FEATURE: Allow running message_bus in a different redis instance (#7616)

Adds `DISCOURSE_MESSAGE_BUS_REDIS_ENABLED` env var, that when set
to true, will allow Discourse to connect to a different redis
instance for MessageBus needs.

When enabled you can configure the same env vars user for redis,
but prefixed by `MESSAGE_BUS`, eg:

`DISCOURSE_MESSAGE_BUS_REDIS_HOST`
This commit is contained in:
Rafael dos Santos Silva
2019-05-28 02:52:43 -03:00
committed by Sam
parent 9a232e1a0a
commit 315a38e0e3
3 changed files with 49 additions and 1 deletions

View File

@@ -120,6 +120,30 @@ redis_password =
# skip configuring client id for cloud providers who support no client commands
redis_skip_client_commands = false
# message bus redis server switch
message_bus_redis_enabled = false
# message bus redis server address
message_bus_redis_host = localhost
# message bus redis server port
message_bus_redis_port = 6379
# message bus redis slave server address
message_bus_redis_slave_host =
# message bus redis slave server port
message_bus_redis_slave_port = 6379
# message bus redis database
message_bus_redis_db = 0
# message bus redis password
message_bus_redis_password =
# skip configuring client id for cloud providers who support no client commands
message_bus_redis_skip_client_commands = false
# enable Cross-origin Resource Sharing (CORS) directly at the application level
enable_cors = false
cors_origin = ''