eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions
blumeops/docs/reference/services/docs.md
Erich Blume 64a78422b1
Some checks failed
Deploy Fly.io Proxy / deploy (push) Failing after 9s
Details
Add Fly.io public reverse proxy for docs.eblu.me (#120) 
## Summary

- Adds a Fly.io reverse proxy (`blumeops-proxy`) that tunnels public traffic to homelab services over Tailscale
- First service exposed: `docs.eblu.me` — the Quartz static docs site
- Includes Pulumi IaC for Tailscale auth key/ACLs and Gandi DNS CNAME
- Adds mise tasks (`fly-deploy`, `fly-setup`, `fly-shutoff`) and Forgejo CI workflow

## Key details

- Fly.io Firecracker VMs support TUN devices natively — no userspace networking needed
- Tailscale auth key is `preauthorized=True` to avoid device approval hangs on container restarts
- nginx caches aggressively for the static site; health check is on the default_server block
- ACLs restrict `tag:flyio-proxy` to `tag:k8s` on port 443 only
- DNS CNAME deployed and verified: `docs.eblu.me` → `blumeops-proxy.fly.dev`

## Test plan

- [x] `curl -sf https://blumeops-proxy.fly.dev/healthz` returns `ok`
- [x] `curl -I -H "Host: docs.eblu.me" https://blumeops-proxy.fly.dev/` returns 200 with `X-Cache-Status`
- [x] `curl -I https://docs.eblu.me/` returns 200 with valid Let's Encrypt cert
- [x] `dig forge.ops.eblu.me` still resolves to 100.98.163.89 (private services unaffected)
- [x] Set `FLY_DEPLOY_TOKEN` Forgejo Actions secret for CI auto-deploy

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/120
2026-02-08 02:36:19 -08:00

1.5 KiB
Raw Blame History

title tags
Docs
service
documentation

Docs (Quartz)

Documentation site built with Quartz and served via nginx.

Quick Reference

Property Value
Public URL https://docs.eblu.me
Private URL docs.ops.eblu.me (tailnet only, via caddy)
Namespace docs
Container registry.ops.eblu.me/blumeops/quartz:v1.0.0
Source docs/ directory in blumeops repo
Build Forgejo workflow build-blumeops.yaml
Public proxy flyio-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/

Related