RQWORKER(1)
π NAME π
okay so rqworker is your girl β she's a command line monitor to start an RQ worker π
and she lives in section 1 of the General Commands Manual, so when you see rqworker(1) out in the wild, that's her, that's the one β¨
π¦ SYNOPSIS π¦
rqworker [OPTIONS] [QUEUES]...
like, give her some options, give her some queues, she'll handle it π«Ά
πΈ DESCRIPTION πΈ
So rqworker is a command-line monitor that starts up an RQ worker. She's part of the python-rq module package, iykyk π
And what is a worker, you ask? Bestie. A worker is a Python process that typically runs in the background and exists solely as a work horse π΄ to perform all those lengthy or blocking tasks that you absolutely do not want to be doing inside your web processes. She's the main character doing the heavy lifting so your web app can stay cute and unbothered πβ¨
β¨ OPTIONS β¨
okay this is the part where you take notes, bestie, because there are a LOT of them and every single one is here, no cap π
-b,--burstβ Run in burst mode (quit after all work is done) πββοΈπ¨--logging_levelTEXT β Set logging level--log-formatTEXT β Set the format of the logs--date-formatTEXT β Set the date format of the logs-n,--nameTEXT β Specify a different name π·οΈ--results-ttlINTEGER β Default results timeout to be used--worker-ttlINTEGER β Default worker timeout to be used--maintenance-interval-ttlINTEGER β Maintenance task interval (in seconds) to be used--job-monitoring-intervalINTEGER β Default job monitoring interval to be used--disable-job-desc-loggingβ Turn off description logging.-v,--verboseβ Show more output π£οΈ-q,--quietβ Show less output π€«--sentry-ca-certsTEXT β Path to CRT file for Sentry DSN--sentry-debugTEXT β Enable debug--sentry-dsnTEXTR β Report exceptions to this Sentry DSN--exception-handlerTEXT β Exception handler(s) to use--pidTEXT β Write the process ID number to a file at the specified path-d,--disable-default-exception-handlerβ Disable RQ's default exception handler--max-jobsINTEGER β Maximum number of jobs to execute--max-idle-timeINTEGER β Maximum seconds to stay alive without jobs to execute β³-s,--with-schedulerβ Run worker with scheduler-S,--serializerTEXT β Run worker with custom serializer-ds,--dequeue-strategyTEXT β Sets a custom stratey to dequeue from multiple queues-S,--serializerTEXT β Path to serializer, defaults torq.serializers.DefaultSerializer-P,--pathTEXT β Specify the import path.--connection-classTEXT β Redis client class to use--queue-classTEXT β RQ Queue class to use-j,--job-classβ RQ Job class to use-w,--worker-classTEXT β RQ Worker class to use-c,--configTEXT β Module containing RQ settings.-u,--urlTEXT β URL describing Redis connection details.--helpβ Show help message and exit.
π bestie not me noticing a couple of lil quirks in the source:-S,--serializeris listed twice (once as "Run worker with custom serializer", once as "Path to serializer, defaults torq.serializers.DefaultSerializer"), the dequeue strategy one says "stratey",--sentry-dsntakes TEXTR, and the-j,--job-classline has its placeholder all smooshed up against the description asTEXTRQ Job class to use. We're reporting, not fixing β the facts stay exactly as written π
π₯ SEE ALSO π₯
and that's the whole page, periodt π this one came out of User Commands β RQWORKER(1), section 1, General Commands Manual, authored under the python-rq crew's name and shipped with the package, dated however old your copy is π go start a worker and slay, bestie ππ¦
π¦ where this page comes from
- debian trixie: python3-rq 2.3.3-2 Β· BSD-2-Clause
- ubuntu noble: python3-rq 1.16.1-1 Β· BSD-2-Clause
- ubuntu questing: python3-rq 2.3.3-2
- ubuntu resolute: python3-rq 2.7-1 Β· BSD-2-Clause
- ubuntu stonking: python3-rq 2.11-1 Β· BSD-2-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms