mirror of
https://github.com/hanzoai/dataroom.git
synced 2026-10-30 18:41:07 +00:00
zooqueen
5dc97c7dad
The repo had no working way to build. .hanzo/workflows/deploy.yml called buildctl-daemonless.sh, which no runner on this fleet carries — jobs run on catthehacker/ubuntu:act-24.04 — so its build step failed in zero seconds with checkout green, which reads as a broken Dockerfile rather than a missing binary. Its second step patched app/dataroom, a CR kind deleted along with infra/k8s/operator/crs. Neither half could work, and a push reported both. hanzo.yml is how every other repo here builds: the forge's system webhook reads it at the pushed sha and schedules one BuildKit job per images: entry. No deploy: block — the tag that reaches the cluster is pinned in universe at charts/app/values/hanzo/dataroom.yaml, and a second writer for one field is the thing that moves an image off the bytes someone just verified. Riding along, because both are compiled into the image and this is the build that ships it: welcome/next.tsx greeted every new user with "Papermark" as a bare literal, on both /welcome and /documents/new. It now reads APP_NAME from lib/branding.ts, which is where the app's name already lives. public/_static/meta-image.png was the upstream wordmark and tagline. It is the default og:image for the root layout, _app, and five auth pages, and lib/utils.ts hardcodes its absolute URL — so every unfurled link to this app, in Slack or iMessage or anywhere else, showed another product's name. Replaced with the same mark and type the login page already uses, at 1200x630. The dynamic /api/og routes were already correct; only the static default was stale.
28 lines
1.3 KiB
YAML
28 lines
1.3 KiB
YAML
# Hanzo CI/CD — dataroom.
|
|
#
|
|
# One image, built by platform.hanzo.ai: the forge's system webhook reads this
|
|
# file at the pushed sha and schedules a BuildKit job per `images:` entry. That
|
|
# is the estate's one way to build, and this repo had no working entry into it.
|
|
#
|
|
# What was here instead was .hanzo/workflows/deploy.yml, which called
|
|
# `buildctl-daemonless.sh` directly. No runner on this fleet carries buildctl —
|
|
# the jobs run on catthehacker/ubuntu:act-24.04 — so the build step failed in
|
|
# zero seconds while checkout passed, which reads as a broken Dockerfile rather
|
|
# than a missing binary. Its second step then patched `app/dataroom`, a CR kind
|
|
# deleted with infra/k8s/operator/crs; dataroom is declared today at
|
|
# universe charts/app/values/hanzo/dataroom.yaml. So the lane could neither
|
|
# build nor deploy, and a push looked like it had done both.
|
|
#
|
|
# No `deploy:` block on purpose. The tag that reaches the cluster is the one
|
|
# pinned in that values file, and a deploy here would be a second authority
|
|
# over the same field.
|
|
|
|
images:
|
|
- name: dataroom
|
|
context: .
|
|
dockerfile: Dockerfile
|
|
repo: ghcr.io/hanzoai/dataroom
|
|
# The cluster has no arm64 nodes; a second arch here is a QEMU-emulated
|
|
# Next.js build for a consumer that does not exist.
|
|
platforms: [linux/amd64]
|