Erich Blume b197bd5f58 Adopt Dagger CI for docs build (Phase 2) (#157 )

## Summary

Migrates the docs build pipeline to Dagger (Phase 2 of the Dagger CI adoption plan).

- **Backfill `date-modified` frontmatter** on all 80 docs — Dagger's `--src=.` excludes `.git`, so Quartz can't use git history for page dates. Frontmatter dates work with or without git.
- **New `docs-check-frontmatter` mise task + pre-commit hook** — validates all docs have `title`, `tags`, and `date-modified`
- **New Dagger functions** — `build_changelog` (towncrier in Python container) and `build_docs` (chains changelog → Quartz build in Node container, returns tarball)
- **Simplified CI workflow** — the ~44-line inline Quartz build (clone, npm ci, build, tar, cleanup) is replaced by `dagger call build-docs`. Changelog step remains local on the runner since towncrier needs to modify the host working tree for the git commit.

### Design decisions

- **Towncrier runs twice in CI**: once inside Dagger (for the docs tarball) and once on the runner (for the git commit). This is intentional — Dagger's directory export is additive and can't delete the consumed changelog fragments from the host.
- **Artifact hosting stays on Forgejo Releases** (not migrated to Forgejo Packages as the plan doc originally suggested). That migration can happen independently.
- **`date-modified` frontmatter** preserved even though `build_changelog` installs git — the git there is only for towncrier's `git add` call, not for history. The local iteration story (`dagger call build-docs --src=. --version=dev` with uncommitted changes) depends on frontmatter dates.

### Local iteration

```bash
dagger call build-docs --src=. --version=dev export --path=./docs-dev.tar.gz
tar tf docs-dev.tar.gz | head -20
```

## Deployment and Testing

- [x] `dagger call build-docs --src=. --version=dev` produces valid 1.1MB tarball (149 HTML pages)
- [x] Pre-commit hooks pass (including new `docs-check-frontmatter`)
- [ ] Full `workflow_dispatch` run after merge

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/157

2026-02-11 16:33:16 -08:00

1.4 KiB

Raw Blame History

title

date-modified

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:

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

backups - Full backup policy
sifaka - Backup target
postgresql - Database backups
restore-1password-backup - Recover 1Password from backup

1.4 KiB Raw Blame History