mirror of
https://github.com/hanzoai/build-demo.git
synced 2026-09-30 20:48:40 +00:00
zeekayandHanzo Dev
75a45a3b92
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]>
23 lines
1007 B
YAML
23 lines
1007 B
YAML
# The build recipe. ONE declaration, read by hanzoai/ci (GitHub lane) and by
|
|
# platform.hanzo.ai (POST /v1/runner, in-cluster) — neither of which needs a
|
|
# Dockerfile, because neither of these artifacts is a container image.
|
|
#
|
|
# `main:` is the zero-config Go lane. `run:` + `out:` is every other toolchain:
|
|
# the command that builds, and the glob of what it produced. `image:` names the
|
|
# toolchain the platform runs that command in (on a GitHub runner the toolchain
|
|
# is the runner, so the GitHub lane ignores it).
|
|
binaries:
|
|
- name: hanzo-demo
|
|
main: ./cmd/demo
|
|
platforms: [linux/amd64, darwin/arm64]
|
|
|
|
- name: hanzo-demo-sdk
|
|
image: node:22-bookworm
|
|
run: npm install --no-audit --no-fund --loglevel=error && npm run build && npm pack --pack-destination .
|
|
out: "*.tgz"
|
|
|
|
# Where the artifacts land: hanzoai/s3, as
|
|
# https://s3.hanzo.ai/plugins/<owner>/<repo>/<tag>/ with a binaries.json index
|
|
# beside them (url + sha256 for each), which is the one file a host reads.
|
|
bucket: plugins
|