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
38 lines
877 B
Markdown
38 lines
877 B
Markdown
---
|
|
title: ArgoCD
|
|
date-modified: 2026-02-07
|
|
tags:
|
|
- service
|
|
- gitops
|
|
---
|
|
|
|
# ArgoCD
|
|
|
|
GitOps continuous delivery platform for the [[cluster|Kubernetes cluster]].
|
|
|
|
## Quick Reference
|
|
|
|
| Property | Value |
|
|
|----------|-------|
|
|
| **URL** | https://argocd.ops.eblu.me |
|
|
| **Tailscale URL** | https://argocd.tail8d86e.ts.net |
|
|
| **Namespace** | `argocd` |
|
|
| **Git Source** | `ssh://forgejo@indri.tail8d86e.ts.net:2200/eblume/blumeops.git` |
|
|
| **Manifests Path** | `argocd/` |
|
|
|
|
## Sync Policy
|
|
|
|
| Application | Sync Policy | Rationale |
|
|
|-------------|-------------|-----------|
|
|
| `apps` | Automated | Picks up new Application manifests |
|
|
| All workloads | Manual | Explicit control over deployments |
|
|
|
|
## Credentials
|
|
|
|
- Admin password: 1Password (blumeops vault)
|
|
- Git deploy key (SSH): 1Password
|
|
|
|
## Related
|
|
|
|
- [[apps|Apps]] - Full application registry
|
|
- [[forgejo]] - Git source
|