Files
zeekay 8b3c902075 Publish the console as hanzo-kms, since kms is a reserved slug
The first run on the GitHub plane gated and built the console, then the
publish stopped at "ensure project kms returned HTTP 400: slug is a
reserved subdomain and cannot be used". The admin console publishes as
hanzo-admin for the same reason; this one is hanzo-kms, and universe's
kms-static root follows it.
2026-10-16 22:47:18 -07:00

32 lines
1.0 KiB
YAML

# Read by hanzoai/ci build.yml@v2 (.github/workflows/cicd.yml).
test:
- name: go
run: go test ./...
- name: console
run: cd frontend && pnpm install --frozen-lockfile && pnpm test && pnpm typecheck
# Each image states its version: the next patch after the newest tag published
# to its repository, so a build never lands on a tag that already names bytes.
images:
- name: kms
context: .
dockerfile: Dockerfile
repo: ghcr.io/hanzoai/kms
version: 2.6.8
- name: kms-fetch
context: .
dockerfile: Dockerfile.kms-fetch
repo: ghcr.io/hanzoai/kms-fetch
version: 0.1.1
# The console at kms.hanzo.ai: s3://hanzo-sites/hanzo/hanzo-kms, which universe
# static-sites.yaml `kms-static` serves. `hanzo-kms`, as the admin console is
# `hanzo-admin`: `kms` is a reserved subdomain, and /v1/projects refuses it as a
# slug ("slug is a reserved subdomain and cannot be used").
site:
slug: hanzo-kms
dir: frontend/dist
build: cd frontend && pnpm install --frozen-lockfile && pnpm build
on: [main]