zeekayandHanzo Dev
9243dc2f96
The tag publisher was deleted this morning without a replacement, so @hanzo/logo had no producer anywhere: no workflow, no failing run, just a package that would stop moving. It is back at .hanzo/workflows/publish.yml where the forge reads it, with two changes and no others. It reads NPM_TOKEN, the one secret name every other Hanzo repo uses, instead of a second name for the same credential. And it no longer writes a GitHub Release: the forge does not serve that API, and the step ran after a successful publish, so it would have turned a shipped package red. .github/workflows now holds the canonical sync.yml alone — refs to git.hanzo.ai and nothing else. The site follows the same shape as every other Hanzo surface: index.html is self-contained, so the Dockerfile copies it into ghcr.io/hanzoai/static with no build stage, and deploy.yml publishes ghcr.io/hanzoai/logo:<sha> without deploying it. hanzoai/universe crs/logo.yaml names the tag that serves and is inert until a human pins one. Replaces a gh-pages push for a Pages site that was never configured — logo.hanzo.ai has answered 404 from our own ingress the whole time. Co-authored-by: Hanzo Dev <dev@hanzo.ai>
10 lines
527 B
Docker
10 lines
527 B
Docker
# logo.hanzo.ai — the logo page, served by hanzoai/static (a Go binary on
|
|
# scratch) behind hanzoai/ingress. No nginx, no GitHub Pages, no CF Pages: the
|
|
# site is an image the operator runs like every other Hanzo surface.
|
|
#
|
|
# index.html is the whole site: one self-contained page, inline CSS, no scripts
|
|
# and no local subresources. There is nothing to build, so there is no build
|
|
# stage — a compile step here would exist only to look like the others.
|
|
FROM ghcr.io/hanzoai/static:v0.5.1
|
|
COPY index.html /public/index.html
|