Switch to filename-based wiki-links (Quartz resolves by filename)

- Convert all wiki-links from title-based to filename-based
- Update doc-links to validate against filenames
- Add doc-filenames task for duplicate filename detection
- Consolidate doc hooks into single local block in pre-commit config

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Erich Blume 2026-02-03 16:29:31 -08:00
commit 9630655cc9
28 changed files with 166 additions and 149 deletions

View file

@ -7,7 +7,7 @@ tags:
# ArgoCD
GitOps continuous delivery platform for the [[kubernetes-cluster | Kubernetes cluster]].
GitOps continuous delivery platform for the [[cluster | Kubernetes cluster]].
## Quick Reference
@ -33,5 +33,5 @@ GitOps continuous delivery platform for the [[kubernetes-cluster | Kubernetes cl
## Related
- [[argocd-applications | Apps]] - Full application registry
- [[apps | Apps]] - Full application registry
- [[forgejo]] - Git source

View file

@ -16,7 +16,7 @@ Daily backup system using Borg backup, running on indri.
| **Install** | mise (pipx) |
| **Config** | `~/.config/borgmatic/config.yaml` |
| **Schedule** | Daily at 2:00 AM |
| **Repository** | `/Volumes/backups/borg/` on [[sifaka-nas | Sifaka]] |
| **Repository** | `/Volumes/backups/borg/` on [[sifaka | Sifaka]] |
## What Gets Backed Up
@ -55,6 +55,6 @@ Dashboard: "Borgmatic Backups" in [[grafana]]
## Related
- [[backup-policy | Backups]] - Full backup policy
- [[sifaka-nas | Sifaka]] - Backup target
- [[backups | Backups]] - Full backup policy
- [[sifaka | Sifaka]] - Backup target
- [[postgresql]] - Database backups

View file

@ -47,4 +47,4 @@ Optional annotation: `grafana_folder: "FolderName"`
- [[prometheus]] - Metrics datasource
- [[loki]] - Logs datasource
- [[grafana-alloy | Alloy]] - Data collector
- [[alloy | Alloy]] - Data collector

View file

@ -17,10 +17,10 @@ Self-hosted photo and video management.
| **Namespace** | `immich` |
| **Deployment** | Helm chart (k8s) |
| **Database** | [[postgresql]] (CNPG) |
| **Storage** | [[sifaka-nas | Sifaka]] photos volume |
| **Storage** | [[sifaka | Sifaka]] photos volume |
## Related
- [[postgresql]] - Database backend
- [[sifaka-nas | Sifaka]] - Photo storage
- [[sifaka | Sifaka]] - Photo storage
- [[jellyfin]] - Video streaming (separate service)

View file

@ -42,10 +42,10 @@ Dashboard > Playback:
## Observability
- Metrics: `jellyfin_metrics` ansible role
- Logs: Forwarded via [[grafana-alloy | Alloy]]
- Logs: Forwarded via [[alloy | Alloy]]
- Dashboard: "Jellyfin Media Server" in [[grafana]]
## Related
- [[navidrome]] - Music streaming
- [[sifaka-nas | Sifaka]] - Media storage
- [[sifaka | Sifaka]] - Media storage

View file

@ -17,7 +17,7 @@ Offline Wikipedia and ZIM archive server.
| **Tailscale URL** | https://kiwix.tail8d86e.ts.net |
| **Namespace** | `kiwix` |
| **Image** | `ghcr.io/kiwix/kiwix-serve:3.8.1` |
| **Storage** | NFS from [[sifaka-nas | Sifaka]] (`/volume1/torrents`) |
| **Storage** | NFS from [[sifaka | Sifaka]] (`/volume1/torrents`) |
## Architecture
@ -49,4 +49,4 @@ Full list: `argocd/manifests/kiwix/configmap-zim-torrents.yaml`
## Related
- [[transmission]] - Downloads ZIM files
- [[sifaka-nas | Sifaka]] - ZIM storage
- [[sifaka | Sifaka]] - ZIM storage

View file

@ -24,7 +24,7 @@ Log aggregation system for BlumeOps infrastructure.
- Single-node deployment with filesystem storage
- TSDB index with 24h period
- Logs collected by [[grafana-alloy | Alloy]] and pushed via Loki API
- Logs collected by [[alloy | Alloy]] and pushed via Loki API
- Queried via [[grafana]]
## Log Sources
@ -46,6 +46,6 @@ Log aggregation system for BlumeOps infrastructure.
## Related
- [[grafana-alloy | Alloy]] - Log collector
- [[alloy | Alloy]] - Log collector
- [[grafana]] - Log visualization
- [[prometheus]] - Metrics counterpart

View file

@ -39,4 +39,4 @@ The `/data` directory contains SQLite database, configuration, and cache.
## Related
- [[jellyfin]] - Video streaming
- [[sifaka-nas | Sifaka]] - Music storage
- [[sifaka | Sifaka]] - Music storage

View file

@ -23,19 +23,19 @@ Metrics storage and querying for BlumeOps infrastructure.
## Data Sources
### Remote Write (from Alloy)
- Indri system metrics via [[grafana-alloy | Alloy]] remote_write
- Indri system metrics via [[alloy | Alloy]] remote_write
- Textfile metrics: minikube, borgmatic, zot, jellyfin
### Scrape Targets
| Target | Metrics |
|--------|---------|
| `sifaka:9100` | [[sifaka-nas | Sifaka]] NAS (node_exporter) |
| `sifaka:9100` | [[sifaka | Sifaka]] NAS (node_exporter) |
| `cnpg-metrics.tail8d86e.ts.net:9187` | [[postgresql | CloudNativePG]] metrics |
| `kube-state-metrics.monitoring.svc:8080` | Kubernetes resource metrics |
## Related
- [[grafana-alloy | Alloy]] - Metrics collector
- [[alloy | Alloy]] - Metrics collector
- [[grafana]] - Visualization
- [[loki]] - Logs counterpart

View file

@ -17,7 +17,7 @@ BitTorrent daemon, primarily for downloading ZIM archives for [[kiwix]].
| **Tailscale URL** | https://torrent.tail8d86e.ts.net |
| **Namespace** | `torrent` |
| **Image** | `lscr.io/linuxserver/transmission:latest` |
| **Storage** | NFS PVC from [[sifaka-nas | Sifaka]] |
| **Storage** | NFS PVC from [[sifaka | Sifaka]] |
## Storage Layout
@ -43,11 +43,11 @@ When downloads complete, the zim-watcher CronJob detects new ZIMs and restarts K
## Monitoring
Basic uptime via blackbox probe in [[grafana-alloy | Alloy]] k8s (Services Health dashboard).
Basic uptime via blackbox probe in [[alloy | Alloy]] k8s (Services Health dashboard).
Web UI shows: active/seeding/paused counts, speeds, disk usage.
## Related
- [[kiwix]] - ZIM archive consumer
- [[sifaka-nas | Sifaka]] - Download storage
- [[sifaka | Sifaka]] - Download storage

View file

@ -30,7 +30,7 @@ OCI-native container registry providing pull-through cache and private image sto
## Pull-Through Cache
When [[kubernetes-cluster | minikube]] pulls an image, containerd checks zot first. If cached, returns immediately. If not, zot fetches from upstream, caches it, then returns.
When [[cluster | minikube]] pulls an image, containerd checks zot first. If cached, returns immediately. If not, zot fetches from upstream, caches it, then returns.
## Security Model
@ -39,4 +39,4 @@ Network access only (no authentication). Defense is the Tailscale ACL boundary.
## Related
- [[forgejo]] - Container build CI
- [[kubernetes-cluster | Cluster]] - Registry consumer
- [[cluster | Cluster]] - Registry consumer