beaverhabits v0.1.0

Apps

Beaver Habit Tracker — a minimal, self-hosted habit tracker without "goals": add habits, tap to check them off, and watch your streaks and heatmaps grow. Deployed as a host-networked Nomad service using SQLite with a persistent data volume.

nomad-pack run beaverhabits --registry nomploy

…or one line (add registry + run)

curl -fsSL https://packs.nomploy.com/install.sh | sh -s -- beaverhabits

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

Source ↗ Project ↗ ★ 1.8k ⚑ Report an issue

1 task http 8080 1 volume image daya0576/beaverhabits:latest tracks :latest image bumped today

Variables 9

values.hcl

Save as values.hcl, edit, then run:

nomad-pack run beaverhabits -f values.hcl --registry nomploy

# The name of the Nomad job.
job_name = "beaverhabits"

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

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

# The Beaver Habit Tracker container image. Pin a tag in production.
image = "daya0576/beaverhabits:latest"

# Host port for the web UI. The container listens on 8080.
port = 8080

# Storage backend (HABITS_STORAGE): DATABASE (single SQLite db) or USER_DISK (a JSON file per user).
storage = "DATABASE"

# Named volume for habit data (/app/.user): the SQLite database or per-user JSON files.
data_volume = "beaverhabits_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 Beaver Habits task.
resources = {
    cpu    = 300
    memory = 256
  }

Name	Type	Default	Description
job_name	string	"beaverhabits"	The name of the Nomad job.
namespace	string	"default"	The Nomad namespace to deploy into.
datacenters	list	["*"]	The datacenters to deploy to.
image	string	"daya0576/beaverhabits:latest"	The Beaver Habit Tracker container image. Pin a tag in production.
port	number	8080	Host port for the web UI. The container listens on 8080.
storage	string	"DATABASE"	Storage backend (HABITS_STORAGE): DATABASE (single SQLite db) or USER_DISK (a JSON file per user).
data_volume	string	"beaverhabits_data"	Named volume for habit data (/app/.user): the SQLite database or per-user JSON files.
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 = 300 memory = 256 }	Resources for the Beaver Habits task.

Back up this pack

This pack stores data in one Docker named volume: beaverhabits_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/beaverhabits_data/_data

rclone (sync to S3/R2)

rclone sync /var/lib/docker/volumes/beaverhabits_data/_data backup:<bucket>/beaverhabits_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.

Readme

beaverhabits

Beaver Habit Tracker — a minimal, self-hosted habit tracker "without goals." Add habits, tap to check them off each day, and watch your streaks and heatmaps build up. Clean UI, mobile-friendly, and a small REST API for automation.

Single host-networked Nomad service using SQLite with a persistent data volume.

Deploy

nomad-pack registry add nomploy https://github.com/Nomploy/nomad-packs
nomad-pack run beaverhabits --registry=nomploy

Configure

Variable	Default	Description
`port`	`8080`	Web UI port. The container listens on 8080.
`storage`	`DATABASE`	`HABITS_STORAGE`: `DATABASE` (single SQLite db) or `USER_DISK` (JSON file per user).
`data_volume`	`beaverhabits_data`	`/app/.user` — the database or per-user files.
`image`	`daya0576/beaverhabits:latest`	Container image. Pin a tag in production.
`resources`	`{ cpu = 300, memory = 256 }`	Task resources.

Register an account on first visit, then add habits and tap the day cells. A REST API is available for automation (e.g. phone shortcuts / cron). Serves plain HTTP — front it with a reverse proxy for TLS. Pin the job to the node holding the volume with constraints.