Refactor internal Redis queues usages #160

New Issue

Closed

opened 2022-07-05 01:39:01 +02:00 by blacklight · 0 comments

blacklight commented

2022-07-05 01:39:01 +02:00

Owner

Created by: BlackLight

Some backends and plugins currently use Redis to synchronize messages to make sure that they can communicate to each other even if they live in different processes (e.g. main Platypush process and HTTP server).

However, some use the default Redis() constructor to initialize the queue object.

Replace the default constructor references with references to get_plugin('redis') to make sure that things work even if Redis is configured on another port or with user/password.

*Created by: BlackLight* Some backends and plugins currently use Redis to synchronize messages to make sure that they can communicate to each other even if they live in different processes (e.g. main Platypush process and HTTP server). However, some use the default `Redis()` constructor to initialize the queue object. Replace the default constructor references with references to `get_plugin('redis')` to make sure that things work even if Redis is configured on another port or with user/password.