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

Grafana

Dashboards and visualization for BlumeOps observability.

Quick Reference

Property	Value
URL	https://grafana.ops.eblu.me
Tailscale URL	https://grafana.tail8d86e.ts.net
Namespace	`monitoring`
Helm Chart	grafana (mirrored to forge)
Values	`argocd/manifests/grafana/values.yaml`

Datasources

Name	Type	Target
Prometheus	prometheus	`prometheus.monitoring.svc.cluster.local:9090`
Loki	loki	`loki.monitoring.svc.cluster.local:3100`
TeslaMate	postgres	`blumeops-pg-rw.databases.svc.cluster.local:5432`

Dashboard Provisioning

Dashboards are ConfigMaps with label grafana_dashboard: "1".

Location: argocd/manifests/grafana-config/dashboards/

Optional annotation: grafana_folder: "FolderName"

Key Dashboards

macOS System - Host metrics for indri
Minikube - Kubernetes cluster overview
Borgmatic Backups - Backup status and trends
Services Health - HTTP probe results
Docs APM - Request rate, latency, cache for docs.eblu.me
Fly.io Proxy Health - Aggregate proxy health across all upstream services
TeslaMate (18 dashboards) - Vehicle data

prometheus - Metrics datasource
loki - Logs datasource
alloy - Data collector

1.4 KiB Raw Blame History