Homelab / Architecture

Website

How root-files.net is delivered — a curated Hugo portfolio from Forgejo, a private GitHub mirror, and Cloudflare Pages.

This page is part of the lab itself: root-files.net presents the homelab as a curated portfolio — not as an operations dashboard and not as a mirror of the wiki or internal homepage.

Purpose

  • Portfolio — architecture, services, hardware, storage, news, and selected ops-AI examples
  • Scrubbed — no internal hostnames, IPs, Vault paths, or reachability hints
  • Bilingual — German and English from the same curated sources

What is deliberately omitted: runbooks, admin UIs, and “here’s how you mount it”.

Delivery pipeline

Forgejo is first the source of truth for all lab code (IaC, docs, CI). The portfolio site is only one delivery chain from that SoT: day-to-day work lives in self-hosted Git; from there a private push mirror syncs to GitHub. Cloudflare Pages builds on push with Hugo and publishes public/ at root-files.net.

No manual Wrangler/API deploy as the normal path — publish follows the Git push.

flowchart LR
  catalogs[Curated catalogs]
  forgejo[Forgejo site repo]
  mirror[Private GitHub mirror]
  pages[Cloudflare Pages Hugo]
  live[root-files.net]
  catalogs --> forgejo --> mirror --> pages --> live
Stage Role
Curated catalogs Allowlist for services, news, ops showcases, scrubbed home automation
Forgejo Lab SoT (IaC, docs, CI) and daily work; the site repo is one of them
GitHub (private) Offsite mirror / Pages trigger
Cloudflare Pages Hugo build and CDN for the public site

Content

Two paths feed the pages:

  1. Generators — manifests → site data/ (service tiles, news journal, ops showcases, HA inventory)
  2. Hand-authored markdown — architecture, connectivity, storage, this website story, hardware product pages

Version and journal: curated portfolio version in the footer, build stamp, Homelab News from the 1 August 2026 epoch.

Principles

  1. Allowlist over leaks — only approved fields and copy go public
  2. One delivery chain — Forgejo → mirror → Pages; no parallel hand deploy
  3. Value over mirroring — design and stations explained; operations stay private
  4. Traceable — news, version, and deep links show what moved

More context: Architecture, Services, News.