mirror of https://github.com/hanzoai/build-demo.git synced 2026-09-30 20:48:40 +00:00

T

zeekayandHanzo Dev 75a45a3b92 build-demo: a recipe whose artifacts are a Go binary and an npm package

Two things hanzo.app could not build before: nothing here is a container
image, so nothing here has a Dockerfile. The declaration is the same
hanzo.yml both CI lanes already read.

Co-authored-by: Hanzo Dev <[email protected]>

2026-07-27 22:42:09 -07:00

cmd/demo

build-demo: a recipe whose artifacts are a Go binary and an npm package

2026-07-27 22:42:09 -07:00

src

build-demo: a recipe whose artifacts are a Go binary and an npm package

2026-07-27 22:42:09 -07:00

go.mod

build-demo: a recipe whose artifacts are a Go binary and an npm package

2026-07-27 22:42:09 -07:00

hanzo.yml

build-demo: a recipe whose artifacts are a Go binary and an npm package

2026-07-27 22:42:09 -07:00

package.json

build-demo: a recipe whose artifacts are a Go binary and an npm package

2026-07-27 22:42:09 -07:00

README.md

build-demo: a recipe whose artifacts are a Go binary and an npm package

2026-07-27 22:42:09 -07:00

tsconfig.json

build-demo: a recipe whose artifacts are a Go binary and an npm package

2026-07-27 22:42:09 -07:00

README.md

build-demo

The smallest proof that hanzo.app builds software, not just container images.

hanzo.yml declares two artifacts and no Dockerfile:

hanzo-demo — a static Go binary, cross-built for linux/amd64 and darwin/arm64
@hanzo/build-demo — a real npm package: tsc compiles src/, npm pack tars it

Both are built by POST /v1/runner on the platform's own cluster and published to https://s3.hanzo.ai/plugins/hanzoai/build-demo/<tag>/, with a binaries.json index carrying the URL and SHA-256 of each file.