Nomploy Nomad Packs

← All packs

ezbookkeeping v0.1.0

Finance

ezBookkeeping — a lightweight, self-hosted personal finance and bookkeeping app: accounts, transactions, categories, budgets and reports, with multi-currency and a mobile-friendly UI. Deployed as a single host-networked Nomad service with SQLite storage.

nomad-pack run ezbookkeeping --registry nomploy
…or one line (add registry + run)
curl -fsSL https://packs.nomploy.com/install.sh | sh -s -- ezbookkeeping

Needs nomad-pack on PATH. The script only adds the nomploy registry and runs this pack.

1 task http 8080 2 volumes image mayswind/ezbookkeeping:latest tracks :latest image bumped today
Variables 10
values.hcl

Save as values.hcl, edit, then run:

nomad-pack run ezbookkeeping -f values.hcl --registry nomploy
# The name of the Nomad job.
job_name = "ezbookkeeping"

# The Nomad namespace to deploy into.
namespace = "default"

# The datacenters to deploy to.
datacenters = ["*"]

# The ezBookkeeping container image. Pin a tag in production.
image = "mayswind/ezbookkeeping:latest"

# Host port for the ezBookkeeping web UI.
port = 8080

# Secret key used to sign auth tokens (openssl rand -base64 32). CHANGE THIS and keep it stable.
secret_key = "change_me_secret_key_to_a_long_random_value"

# Named volume for the SQLite database.
data_volume = "ezbookkeeping_data"

# Named volume for uploaded files (avatars, attachments).
storage_volume = "ezbookkeeping_storage"

# Placement constraints. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true".
constraints = []

# Resources for the ezBookkeeping task.
resources = {
    cpu    = 300
    memory = 256
  }
NameTypeDefaultDescription
job_name string
"ezbookkeeping"
The name of the Nomad job.
namespace string
"default"
The Nomad namespace to deploy into.
datacenters list
["*"]
The datacenters to deploy to.
image string
"mayswind/ezbookkeeping:latest"
The ezBookkeeping container image. Pin a tag in production.
port number
8080
Host port for the ezBookkeeping web UI.
secret_key set me string
"change_me_secret_key_to_a_long_random_value"
Secret key used to sign auth tokens (openssl rand -base64 32). CHANGE THIS and keep it stable.
data_volume string
"ezbookkeeping_data"
Named volume for the SQLite database.
storage_volume string
"ezbookkeeping_storage"
Named volume for uploaded files (avatars, attachments).
constraints list
[]
Placement constraints. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true".
resources object
{
    cpu    = 300
    memory = 256
  }
Resources for the ezBookkeeping task.
Back up this pack

This pack stores data in 2 Docker named volumes: ezbookkeeping_dataezbookkeeping_storage

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/ezbookkeeping_data/_data \
  /var/lib/docker/volumes/ezbookkeeping_storage/_data

rclone (sync to S3/R2)

rclone sync /var/lib/docker/volumes/ezbookkeeping_data/_data backup:<bucket>/ezbookkeeping_data
rclone sync /var/lib/docker/volumes/ezbookkeeping_storage/_data backup:<bucket>/ezbookkeeping_storage

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.

Readme

ezbookkeeping

ezBookkeeping is a lightweight, self-hosted personal finance and bookkeeping app — accounts, transactions, categories, budgets and reports, with multi-currency support and a mobile-friendly UI (and a PWA).

This pack runs ezBookkeeping as a single host-networked Nomad job with SQLite storage — no external database is required.

Quick start

nomad-pack run ezbookkeeping --registry=nomploy

Then open http://<node-ip>:8080 and create the first account.

Configuration

Variable Default Notes
port 8080 Web UI host port
secret_key change me Auth token signing key — keep stable

Change secret_key to a long random value before deploying anywhere real and keep it stable across deploys.

Data persists in the ezbookkeeping_data (SQLite) and ezbookkeeping_storage (uploads) named volumes. For MySQL/PostgreSQL instead of SQLite, or other options, override the EBK_* environment variables per the ezBookkeeping configuration docs.