RQWORKER(1)

πŸ“¦
version 2.11 Β· 3 versions
, in debian trixie, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸŽ€ 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_level TEXT β€” Set logging level
  • --log-format TEXT β€” Set the format of the logs
  • --date-format TEXT β€” Set the date format of the logs
  • -n, --name TEXT β€” Specify a different name 🏷️
  • --results-ttl INTEGER β€” Default results timeout to be used
  • --worker-ttl INTEGER β€” Default worker timeout to be used
  • --maintenance-interval-ttl INTEGER β€” Maintenance task interval (in seconds) to be used
  • --job-monitoring-interval INTEGER β€” 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-certs TEXT β€” Path to CRT file for Sentry DSN
  • --sentry-debug TEXT β€” Enable debug
  • --sentry-dsn TEXTR β€” Report exceptions to this Sentry DSN
  • --exception-handler TEXT β€” Exception handler(s) to use
  • --pid TEXT β€” Write the process ID number to a file at the specified path
  • -d, --disable-default-exception-handler β€” Disable RQ's default exception handler
  • --max-jobs INTEGER β€” Maximum number of jobs to execute
  • --max-idle-time INTEGER β€” Maximum seconds to stay alive without jobs to execute ⏳
  • -s, --with-scheduler β€” Run worker with scheduler
  • -S, --serializer TEXT β€” Run worker with custom serializer
  • -ds, --dequeue-strategy TEXT β€” Sets a custom stratey to dequeue from multiple queues
  • -S, --serializer TEXT β€” Path to serializer, defaults to rq.serializers.DefaultSerializer
  • -P, --path TEXT β€” Specify the import path.
  • --connection-class TEXT β€” Redis client class to use
  • --queue-class TEXT β€” RQ Queue class to use
  • -j, --job-class β€” RQ Job class to use
  • -w, --worker-class TEXT β€” RQ Worker class to use
  • -c, --config TEXT β€” Module containing RQ settings.
  • -u, --url TEXT β€” URL describing Redis connection details.
  • --help β€” Show help message and exit.
πŸ’€ bestie not me noticing a couple of lil quirks in the source: -S, --serializer is listed twice (once as "Run worker with custom serializer", once as "Path to serializer, defaults to rq.serializers.DefaultSerializer"), the dequeue strategy one says "stratey", --sentry-dsn takes TEXTR, and the -j, --job-class line has its placeholder all smooshed up against the description as TEXTRQ 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