Worker Keys

Worker Keys

bitmagnet uses a worker architecture where each feature runs as an independent worker. Enable workers by adding --keys=<key> to the command: block in your compose file.

---

Available workers

Worker	Key	Description	Needs config
HTTP server	http_server	Web UI and GraphQL API on port 3333	No
Queue server	queue_server	Processes the classification queue (TMDB, OMDb)	No
DHT crawler	dht_crawler	Crawls the BitTorrent DHT network for new torrents	No
Prowlarr crawler	prowlarr_crawler	Polls configured Prowlarr indexers on a schedule	Yes — see Prowlarr Integration
DB trim	db_trim	Purges old/dead torrents based on per-source rules	Yes — see DB Size Management

---

Common configurations

All-in-one (no VPN):

command:
  - worker
  - run
  - --keys=http_server
  - --keys=queue_server
  - --keys=dht_crawler
  - --keys=prowlarr_crawler
  - --keys=db_trim

Main instance (sidecar deployment — DHT runs in separate container):

command:
  - worker
  - run
  - --keys=http_server
  - --keys=queue_server
  - --keys=prowlarr_crawler
  - --keys=db_trim

DHT sidecar (behind gluetun VPN):

command:
  - worker
  - run
  - --keys=dht_crawler
  - --keys=http_server

The sidecar needs http_server so the main instance can probe its health status. See DHT Sidecar Setup.

---

Note on OMDb

OMDb enrichment is not a separate worker — it runs inline in the classifier pipeline during content processing. Enable it via omdb.enabled and omdb.api_key in config.yml. See OMDb Enrichment.