This blog ships from a peer-to-peer OCI registry

This page is not deployed from a git push. It is an OCI artifact.

How it works

  1. I write the site and run one command on my machine: it builds the manifests and pushes them as an OCI artifact to ocid, a local-first, peer-to-peer OCI registry — flux push artifact oci://127.0.0.1:5050/hugo:v1.
  2. Every push produces a signed release binding the tag to a manifest digest, and every blob is verified against it (BLAKE3 while streaming, sha256 afterwards), so only content I actually published is accepted.
  3. The artifact replicates over ocid’s peer-to-peer network to my cluster, where Flux picks it up from an OCI source and deploys it.

Bump the tag, push again, and the site updates — no git commit needed for content changes.

← all posts