Docs (Quartz)

Documentation site built with Quartz and served via nginx.

Quick Reference

PropertyValue
Public URLhttps://docs.eblu.me
Private URLdocs.ops.eblu.me (tailnet only, via caddy)
Namespacedocs
Containerregistry.ops.eblu.me/blumeops/quartz:v1.0.0
Sourcedocs/ directory in blumeops repo
BuildForgejo workflow build-blumeops.yaml
Public proxyflyio-proxy (Fly.io → Tailscale tunnel)

Architecture

  1. Source: Markdown files in docs/ with Obsidian-compatible wiki-links
  2. Build: Forgejo workflow builds Quartz static site on push to main
  3. Release: Built assets published as Forgejo release attachments
  4. Deploy: Container downloads release bundle on startup, serves via nginx

Release Process

Documentation is automatically built and released when changes are pushed to main:

  1. Workflow detects changes in docs/ directory
  2. Quartz builds static HTML/CSS/JS
  3. Assets uploaded as release attachment
  4. ArgoCD deployment updated with new DOCS_RELEASE_URL
  5. Pod restarts and downloads new bundle

Configuration

  • Quartz config: quartz.config.ts
  • Layout: quartz.layout.ts
  • ArgoCD app: argocd/apps/docs.yaml
  • Manifests: argocd/manifests/docs/