teammapper v0.1.0

Apps

TeamMapper — a simple, self-hosted tool to create and share mind maps and collaborate on them in real time with your team. Deployed as an all-in-one host-networked Nomad job: the TeamMapper app plus a PostgreSQL sidecar with a persistent database volume.

nomad-pack run teammapper --registry nomploy

…or one line (add registry + run)

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

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

Source ↗ Project ↗ ★ 501 ⚑ Report an issue

2 tasks http 3000db 5432 1 volume image ghcr.io/b310-digital/teammapper:main pinned :main image bumped today

Variables 13

values.hcl

Save as values.hcl, edit, then run:

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

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

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

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

# The TeamMapper app image. Pin a tag in production.
image = "ghcr.io/b310-digital/teammapper:main"

# The PostgreSQL image for the bundled database.
postgres_image = "postgres:16-alpine"

# Host port for the TeamMapper web app. The container listens on 3000.
port = 3000

# Host port for the co-located PostgreSQL.
db_port = 5432

# Password for the TeamMapper PostgreSQL user.
db_password = "teammapper"

# Delete mind maps that haven't been accessed for this many days (DELETE_AFTER_DAYS). 0 = never delete.
delete_after_days = 30

# Named volume for PostgreSQL data (/var/lib/postgresql/data). Holds all mind maps.
db_data_volume = "teammapper_db_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 TeamMapper app task.
resources = {
    cpu    = 500
    memory = 512
  }

# Resources for the PostgreSQL task.
postgres_resources = {
    cpu    = 300
    memory = 256
  }

Name	Type	Default	Description
job_name	string	"teammapper"	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/b310-digital/teammapper:main"	The TeamMapper app image. Pin a tag in production.
postgres_image	string	"postgres:16-alpine"	The PostgreSQL image for the bundled database.
port	number	3000	Host port for the TeamMapper web app. The container listens on 3000.
db_port	number	5432	Host port for the co-located PostgreSQL.
db_password key	string	"teammapper"	Password for the TeamMapper PostgreSQL user.
delete_after_days	number	30	Delete mind maps that haven't been accessed for this many days (DELETE_AFTER_DAYS). 0 = never delete.
db_data_volume	string	"teammapper_db_data"	Named volume for PostgreSQL data (/var/lib/postgresql/data). Holds all mind maps.
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 TeamMapper app task.
postgres_resources	object	{ cpu = 300 memory = 256 }	Resources for the PostgreSQL task.

Back up this pack

This pack stores data in one Docker named volume: teammapper_db_data

⚠ This pack bundles a database. A cold copy of the volume can be inconsistent — for a reliable backup, dump the DB (pg_dump / mysqldump) or stop the job while backing up.

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/teammapper_db_data/_data

rclone (sync to S3/R2)

rclone sync /var/lib/docker/volumes/teammapper_db_data/_data backup:<bucket>/teammapper_db_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

teammapper

TeamMapper — a simple, self-hosted tool for creating and sharing mind maps and collaborating on them in real time. Share a map's link and work on it together, no accounts required.

All-in-one host-networked Nomad job: the TeamMapper app plus a PostgreSQL sidecar.

Deploy

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

Configure

Variable	Default	Description
`port`	`3000`	Web app port (`PORT`). The container listens on 3000.
`delete_after_days`	`30`	Prune maps not accessed for N days (`DELETE_AFTER_DAYS`); `0` = never.
`db_password`	`teammapper`	PostgreSQL password.
`db_port`	`5432`	Host port for the bundled PostgreSQL.
`db_data_volume`	`teammapper_db_data`	`/var/lib/postgresql/data` — all mind maps.
`image`	`ghcr.io/b310-digital/teammapper:main`	App image. Pin a tag in production.
`resources` / `postgres_resources`	see `variables.hcl`	Per-task resources.

Open the app, create a map, and share its link to collaborate live. Old, untouched maps are pruned per delete_after_days. Serves plain HTTP — front it with a reverse proxy for TLS. Pin the job to the node holding the volume with constraints.