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.