Homarr — a sleek, self-hosted dashboard for your homelab: a customizable start page with drag-and-drop widgets, live integrations for your apps (Docker, *arr, media servers, and more), and per-user boards. Deployed as a host-networked Nomad service with a persistent data volume.
Needs nomad-pack on PATH. The script only adds the nomploy registry and runs this pack.
Source ↗ Project ↗ ★ 4.8k ⚑ Report an issue
Save as values.hcl, edit, then run:
# The name of the Nomad job.
job_name = "homarr"
# The Nomad namespace to deploy into.
namespace = "default"
# The datacenters to deploy to.
datacenters = ["*"]
# The Homarr container image. Pin a tag in production.
image = "ghcr.io/homarr-labs/homarr:latest"
# Host port for the Homarr web UI. The container listens on 7575.
port = 7575
# 64-character hex key used to encrypt secrets in the database (SECRET_ENCRYPTION_KEY). CHANGE THIS and keep it stable — generate with: openssl rand -hex 32.
secret_encryption_key = "change-me-generate-with-openssl-rand-hex-32-0000000000000000"
# Named volume for Homarr data (/appdata): the database, boards, and config.
data_volume = "homarr_data"
# Placement constraints. Pin to the node holding the volume. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true".
constraints = []
# Resources for the Homarr task.
resources = {
cpu = 500
memory = 512
}
| Name | Type | Default | Description |
|---|---|---|---|
| job_name | string | "homarr" | The name of the Nomad job. |
| namespace | string | "default" | The Nomad namespace to deploy into. |
| datacenters | list | ["*"] | The datacenters to deploy to. |
| image | string | "ghcr.io/homarr-labs/homarr:latest" | The Homarr container image. Pin a tag in production. |
| port | number | 7575 | Host port for the Homarr web UI. The container listens on 7575. |
| secret_encryption_key set me | string | "change-me-generate-with-openssl-rand-hex-32-0000000000000000" | 64-character hex key used to encrypt secrets in the database (SECRET_ENCRYPTION_KEY). CHANGE THIS and keep it stable — generate with: openssl rand -hex 32. |
| data_volume | string | "homarr_data" | Named volume for Homarr data (/appdata): the database, boards, and config. |
| constraints | list | [] | Placement constraints. Pin to the node holding the volume. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true". |
| resources | object | {
cpu = 500
memory = 512
} | Resources for the Homarr task. |
No variables match.
This pack stores data in one Docker named volume:
homarr_data
restic
# Run on the node hosting this pack. Point restic at your repo first: # export RESTIC_REPOSITORY="s3:https://<account>.r2.cloudflarestorage.com/<bucket>" # export RESTIC_PASSWORD="<repo-password>" # export AWS_ACCESS_KEY_ID=<key> AWS_SECRET_ACCESS_KEY=<secret> restic backup \ /var/lib/docker/volumes/homarr_data/_data
rclone (sync to S3/R2)
rclone sync /var/lib/docker/volumes/homarr_data/_data backup:<bucket>/homarr_data
Paths assume the default Docker volume location (/var/lib/docker/volumes). Restore by stopping the job, restoring files into the same volume, and re-running the pack.
Homarr — a sleek, self-hosted dashboard for your homelab. A customizable start page with drag-and-drop widgets, live integrations for your apps (Docker, the *arr suite, media servers, download clients, and more), search, and per-user boards with authentication built in.
Single host-networked Nomad service with a persistent data volume.
nomad-pack registry add nomploy https://github.com/Nomploy/nomad-packs
nomad-pack run homarr --registry=nomploy
| Variable | Default | Description |
|---|---|---|
port |
7575 |
Web UI port (PORT). |
secret_encryption_key |
change-me-… |
64-hex-char key (SECRET_ENCRYPTION_KEY) encrypting stored secrets. Change it and keep it stable (openssl rand -hex 32). |
data_volume |
homarr_data |
/appdata — database, boards, and config. |
image |
ghcr.io/homarr-labs/homarr:latest |
Container image. Pin a tag in production. |
resources |
{ cpu = 500, memory = 512 } |
Task resources. |
Create the admin account on first visit, then build your board and connect integrations. Keep
secret_encryption_key stable — changing it makes stored credentials unreadable. A richer, integration-driven
alternative to the homepage, glance, and flame packs. Serves plain HTTP — front it with a reverse proxy
for TLS. Pin the job to the node holding the volume with constraints.