Backend plugin · listing tai42/backend-rqInstall
Permissions
Provides
rq
Backend — RQ execution backend — background tool runs and schedules over Redis.
RQ is Redis-only like arq, with a worker, a scheduler, and the RQ dashboard.
Enable it
manifest.yml
Configuration
TheRQ_ env group. RQ_REDIS_URL falls back to the shared
TAI_DEFAULT_REDIS_URL when unset; a set RQ_REDIS_URL always wins.
Run the processes
worker runtime runs RQ’s work loop on a dedicated thread, so the process’s
event loop stays free for worker-bus ops. Its lifecycle is the shared one every
backend gets: it waits for the app to finish booting before it consumes, then
SIGTERM (or SIGINT) drains it warm — no new jobs, the current one finishes, the
process exits after teardown — and a second signal kills the running work-horse.
An idle worker stops within one dequeue poll (5s).
beat and dashboard pull no queued work, so they run on the event loop and
keep whatever signal handling their own CLI installs. Nothing else runs in those
processes, so that is deliberate.
Quirks
- RQ has no disabled-schedule state, so
backend_list_schedulesalways reports a schedule as enabled, and disabling one deletes it. backend_registered_tasksandbackend_list_failed_tasksare not implemented.
See also
- Backends — the contract all three shipped backends implement.
- Schedule a tool — putting work on a schedule.