Installation

Installation

torq is one container with an embedded SQLite database. All you need is Docker and a volume for /data.

Docker

docker run -d --name torq --restart unless-stopped \
  -p 8080:8080 \
  -v torq-data:/data \
  -e TZ=Europe/Berlin \
  ghcr.io/marekbeckmann/torq:latest

Images are published for linux/amd64 and linux/arm64 (Raspberry Pi 4/5, ARM servers). Every image is also tagged with its commit, ghcr.io/marekbeckmann/torq:sha-<commit>, so you can pin a version.

Docker Compose

The repository's docker-compose.yml builds the image from source:

git clone https://github.com/marekbeckmann/torq.git
cd torq
docker compose up -d

To use the published image instead, replace build: . with image: ghcr.io/marekbeckmann/torq:latest. Optional settings go into a .env file next to it (see .env.example).

First start

Open http://localhost:8080. torq asks you to create the administrator account.

Important

Create the administrator account right away. Until it exists, anyone who can reach torq can create it. Don't expose a fresh instance to the internet before this step.

The administrator can add more users under Settings → Users. Everyone in a torq instance shares one garage; administrators additionally manage users, webhooks and instance settings.

Behind a reverse proxy

• Set TORQ_BASE_URL to the public https URL. Session cookies then get the Secure flag and notifications link back to torq.
• Set TORQ_TRUSTED_PROXIES to your proxy's address range so login throttling sees real client IPs.
• torq does not terminate TLS itself; let the proxy or a Cloudflare Tunnel do that. See Deployment.

Requirements

• About 30 MB of disk for the image, plus your data and uploads.
• Typically well under 100 MB of RAM; an online catalog update briefly uses more (up to ~200 MB).
• No internet access is needed, except for webhooks and the optional online features (catalog update, spec-sheet auto-fill).