QuantumGhost 2db638b992 Add a configuration for controlling the redis instance / type used for streaming events between celery worker and api (vibe-kanban 08e07904) ...

Currently, the celery worker executing workflows / chatflows uses redis pubsub to publish events to api.
(See \_topic\_msg\_generator and \_publish\_streaming\_response)

The current implementation uses the default redis client.

For large scale deployment, we need to use a dedicated redis cluster to ensure performance.

To achieve this, you should:

1. introduce a dedicated configuration class to control

  the redis address used for pubsub. (Ideally, there should only be one configuration item such as `pubsub_redis_url`, and its default value should be the original redis confugration.)

2. Add an option to switch between pubsub and sharded pubsub. When shared pubsub is specified, the ShardedRedisBroadcastChannel should be used instead.

COmplete the task above, add some unit tests.

2026-01-19 07:40:44 +08:00

..

otel

add service layer OTel Span (#28582)

2025-12-05 21:58:32 +08:00

storage

Removes the 'extensions' directory from pyrightconfig.json and fixes … (#26512)

2025-10-05 15:57:42 +09:00

test_celery_ssl.py

feat: introduce trigger functionality (#27644)

2025-11-12 17:59:37 +08:00

test_ext_request_logging.py

feat: add x-trace-id to http responses and logs (#29015)

2025-12-02 17:22:34 +08:00

test_pubsub_channel.py

Add a configuration for controlling the redis instance / type used for streaming events between celery worker and api (vibe-kanban 08e07904)

2026-01-19 07:40:44 +08:00

test_redis.py

feat: add redis fallback mechanism #21043 (#21044)

2025-07-10 10:19:58 +08:00