Self-host Background Worker + Redis Queue on a VPS
A worker process pulling jobs off a Redis-backed queue, the base shape for async job processing.
levelrail-cli templates deploy worker-redis-queue-starter --name my-worker-redis-queue-starterSpecification
- Status
- Listed
- Category
- Starter Kits
- Services
- queue, worker
- Ports
- none
- Volumes
- 1
- Memory
- about 192 MiB
- arm64
- image published
- amd64
- image published
- Settings to fill in
- none
- License
- not yet recorded
About Background Worker + Redis Queue
A worker process pulling jobs off a Redis-backed queue, the base shape for async job processing. Runs 2 containers (queue, worker) and keeps its data in named volumes.
What it deploys
Background Worker + Redis Queue runs as 2 services in a single Compose app, with 1 named volume mount.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| queue | redis | 7-alpine | none | worker_redis_queue_data -> /data |
| worker | node | 22-alpine | none | none |
Before you install
- CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
- Listed. It is in the catalog. Back up the data volume before changing an image tag.
Settings and environment
You do not have to fill in anything. Values are never shown here.
| Service | Variable | Value |
|---|---|---|
| worker | NODE_ENV | Preset by the template |
| worker | QUEUE_URL | Preset by the template |
Install Background Worker + Redis Queue on a VPS
-
Install Levelrail on a fresh VPS
Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.
curl -fsSL https://levelrail.com/install.sh | sudo sh -
Sign in
Open the setup link, choose a password, then log the CLI in. The CLI install command is
curl -fsSL https://levelrail.com/install-cli.sh | shif the machine does not have it. See Getting started.levelrail-cli login --device -
Read the template
Shows the entry, including its full compose.yaml.
levelrail-cli templates get worker-redis-queue-starter -
Deploy it
This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.
levelrail-cli templates deploy worker-redis-queue-starter --name my-worker-redis-queue-starter
Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Background Worker + Redis Queue.
Docs and upstream
More in Starter Kits
- FastAPI + PostgreSQLA minimal Python HTTP service wired to a Postgres database, the reference pairing for a FastAPI backend.
- Next.js + PostgreSQLThe SSR-plus-database pairing behind most Next.js apps, wired with a healthchecked Postgres.
- Nginx Reverse Proxy (Multi-Backend)One Nginx entrypoint routing to two independent backend services, demonstrating depends_on across three services.
- Node.js API + PostgreSQLA minimal Node HTTP service wired to a Postgres database, the most common backend pairing.
- Redis Cache StarterA web service backed by a Redis cache, the cache-aside pattern most apps reach for first.
- Static Site + API BackendA static frontend and a separate API service deployed together, the split most SPAs actually run.