Erich Blume ce59e9951b Fix frontmatter field name: date-modified -> modified

Quartz's CreatedModifiedDate plugin recognizes `modified`, `lastmod`,
`updated`, and `last-modified` — but not `date-modified`. The wrong
field name caused Quartz to fall through to filesystem timestamps
(UTC in Dagger), showing incorrect dates on the rendered site.

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

2026-02-11 16:43:12 -08:00

1.9 KiB

Raw Blame History

title

modified

Backup Policy

Daily automated backups from indri to sifaka NAS.

Schedule

Time	Frequency	System
2:00 AM	Daily	borgmatic

What Gets Backed Up

Directories

Path	Description	Priority
`~/code/personal/zk`	Zettelkasten notes	Critical
`/opt/homebrew/var/forgejo`	Git repositories	Critical
`~/.config/borgmatic`	Backup config	High
`~/Documents`	Personal documents (includes 1password encrypted export)	High

Databases

Database	Host	Method
miniflux	[[postgresql	pg.ops.eblu.me]]
teslamate	[[postgresql	pg.ops.eblu.me]]

Sifaka-Native Data

Some data lives directly on sifaka rather than being backed up to it (photos via immich, music via navidrome, video via jellyfin). See sifaka for data protection details.

What Is NOT Backed Up

Data	Reason
ZIM archives (`~/transmission/`)	Re-downloadable via torrent
Prometheus metrics	Ephemeral, in k8s PVC
Loki logs	Ephemeral, in k8s PVC
devpi cache	Re-fetchable from PyPI

Retention Policy

Period	Retention
Daily	7 backups
Monthly	12 backups
Yearly	1000 backups

Backup Target

Repository: /Volumes/backups/borg/ on sifaka

Monitoring

Metrics exposed to prometheus:

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

Dashboard: "Borgmatic Backups" in grafana

borgmatic - Backup system details
sifaka - Backup storage
postgresql - Database backups
restore-1password-backup - Recover 1Password from backup

1.9 KiB Raw Blame History