## Summary - Rename `date-modified` -> `modified` in all 80 docs and the `docs-check-frontmatter` task Quartz's `CreatedModifiedDate` plugin recognizes `modified`, `lastmod`, `updated`, and `last-modified` — but not `date-modified`. The wrong field name caused Quartz to ignore frontmatter dates entirely and fall through to filesystem timestamps (UTC inside Dagger), showing Feb 12 on pages built late on Feb 11 PST. ## Test plan - [x] `mise run docs-check-frontmatter` passes - [ ] Kick off docs release after merge — verify rendered dates match frontmatter values Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/158
1.3 KiB
1.3 KiB
| title | modified | tags | ||
|---|---|---|---|---|
| Borgmatic | 2026-02-10 |
|
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 [[sifaka |
What Gets Backed Up
Directories:
~/code/personal/zk- Zettelkasten/opt/homebrew/var/forgejo- Git forge data~/.config/borgmatic- Borgmatic config~/Documents- Personal documents
Databases:
minifluxon postgresqlteslamateon 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 accessibilityborgmatic_last_archive_timestamp- Last backup timeborgmatic_repo_deduplicated_size_bytes- Disk usage
Dashboard: "Borgmatic Backups" in grafana
Related
- backups - Full backup policy
- sifaka - Backup target
- postgresql - Database backups
- restore-1password-backup - Recover 1Password from backup