Erich Blume ce1f696bd8 Add Reference section with 24 technical reference cards

Phase 2 of documentation restructuring. Creates docs/reference/ with:

Services (16):
- alloy, argocd, borgmatic, 1password, forgejo, grafana
- jellyfin, kiwix, loki, miniflux, navidrome, postgresql
- prometheus, teslamate, transmission, zot

Infrastructure (3):
- hosts - Device inventory
- tailscale - ACLs, groups, tags
- routing - DNS domains and port mappings

Kubernetes (2):
- cluster - Minikube specs
- apps - ArgoCD application registry

Storage (2):
- sifaka - Synology NAS configuration
- backups - Backup policy

All cards use wiki-links for cross-referencing and include YAML
frontmatter with title and tags for Quartz.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-02-03 13:22:19 -08:00

1.4 KiB

Raw Blame History

title

Borgmatic

Daily backup system using Borg backup, running on indri.

Quick Reference

Property	Value
Install	mise (pipx)
Config	`~/.config/borgmatic/config.yaml`
Schedule	Daily at 2:00 AM
Repository	`/Volumes/backups/borg/` on storage/sifaka

What Gets Backed Up

Directories:

~/code/personal/zk - Zettelkasten
/opt/homebrew/var/forgejo - Git forge data
~/.config/borgmatic - Borgmatic config
~/Documents - Personal documents
~/Pictures - Photos

Databases:

miniflux on postgresql
teslamate on postgresql

Not backed up (by design):

ZIM archives (re-downloadable)
Prometheus metrics (ephemeral)
Loki logs (ephemeral)

Retention Policy

Period	Count
Daily	7
Monthly	12
Yearly	1000

Monitoring

Metrics exposed via textfile collector to prometheus:

borgmatic_up - Repository accessibility
borgmatic_last_archive_timestamp - Last backup time
borgmatic_repo_deduplicated_size_bytes - Disk usage

Dashboard: "Borgmatic Backups" in grafana

storage/backups - Full backup policy
storage/sifaka - Backup target
postgresql - Database backups

1.4 KiB Raw Blame History