Self-host Background Worker + Redis Queue with Levelrail
A worker process pulling jobs off a Redis-backed queue, the base shape for async job processing.
- Memory192 MiB
- Archarm64
- Services2
How to self-host Background Worker + Redis Queue
-
Pull the images
2 images are pulled on your server.
Show images
redis:7-alpinenode:22-alpine
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data.
-
Fill in the secrets
2 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Background Worker + Redis Queue requirements
- Memory
- About 192 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- none
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Background Worker + Redis Queue. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Background Worker + Redis Queue docs page.
Deploy Background Worker + Redis Queue your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Background Worker + Redis Queue from the CLI
levelrail-cli templates deploy worker-redis-queue-starter --name my-worker-redis-queue-starter Deploy Background Worker + Redis Queue with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/worker-redis-queue-starter/deploy Background Worker + Redis Queue configuration
Background Worker + Redis Queue services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| queue | redis:7-alpine | none | worker_redis_queue_data -> /data |
| worker | node:22-alpine | none | none |
Background Worker + Redis Queue environment variables
| Variable | Service | Value |
|---|---|---|
| NODE_ENV | worker | Preset by the template |
| QUEUE_URL | worker | Preset by the template |
Ports and volumes
- Ports
- none
- Volumes
- 1 named mount: worker_redis_queue_data -> /data
Background Worker + Redis Queue FAQ
How much memory does Background Worker + Redis Queue need?
The catalog lists about 192 MiB of memory for Background Worker + Redis Queue across its 2 services.
Does Background Worker + Redis Queue run on arm64?
For Background Worker + Redis Queue, an arm64 image is published; amd64 is image published.
Does Background Worker + Redis Queue need configuration before it starts?
No. The template fills in its own defaults.
Which database does Background Worker + Redis Queue bundle?
The template includes Redis, running as its own service.
Where does Background Worker + Redis Queue keep its data?
In a named volume: worker_redis_queue_data mounted at /data.
Can I deploy Background Worker + Redis Queue on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Background Worker + Redis Queue, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image redis:7-alpine, node:22-alpine is what you deploy there.