Erich Blume
b197bd5f58
## 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
56 lines
1.3 KiB
Markdown
56 lines
1.3 KiB
Markdown
---
|
|
title: Loki
|
|
date-modified: 2026-02-08
|
|
tags:
|
|
- service
|
|
- observability
|
|
---
|
|
|
|
# Loki
|
|
|
|
Log aggregation system for BlumeOps infrastructure.
|
|
|
|
## Quick Reference
|
|
|
|
| Property | Value |
|
|
|----------|-------|
|
|
| **URL** | https://loki.ops.eblu.me |
|
|
| **Tailscale URL** | https://loki.tail8d86e.ts.net |
|
|
| **Namespace** | `monitoring` |
|
|
| **Image** | `grafana/loki:3.4.2` |
|
|
| **Storage** | 50Gi PVC |
|
|
| **Retention** | 31 days |
|
|
|
|
## Architecture
|
|
|
|
- Single-node deployment with filesystem storage
|
|
- TSDB index with 24h period
|
|
- Logs collected by [[alloy|Alloy]] and pushed via Loki API
|
|
- Queried via [[grafana]]
|
|
|
|
## Log Sources
|
|
|
|
**From Indri (via Alloy):**
|
|
- forgejo, tailscale (brew services)
|
|
- alloy, borgmatic, zot, jellyfin (LaunchAgents)
|
|
|
|
**From Kubernetes (via Alloy DaemonSet):**
|
|
- All pods in all namespaces
|
|
|
|
**From Fly.io proxy (via embedded Alloy):**
|
|
- nginx JSON access logs (`{instance="flyio-proxy", job="flyio-nginx"}`)
|
|
|
|
## Query Examples (LogQL)
|
|
|
|
```logql
|
|
{service="forgejo"} # All forgejo logs
|
|
{service="borgmatic", stream="stderr"} # Borgmatic errors
|
|
{host="indri"} |= "error" # All logs containing "error"
|
|
{instance="flyio-proxy"} |= "docs.eblu.me" # Fly.io proxy access logs for docs
|
|
```
|
|
|
|
## Related
|
|
|
|
- [[alloy|Alloy]] - Log collector
|
|
- [[grafana]] - Log visualization
|
|
- [[prometheus]] - Metrics counterpart
|