Files
zooqueen f89340860e band-setlist: Setlist — public show & setlist tracker on the Hanzo stack
Gig-poster-brutalist band gig log: browse upcoming/past shows, open a show
to read its ordered setlist, and sign in to log shows + build sets.

- UI: 100% @hanzo/gui primitives (Tamagui longhand), no Tailwind
- Auth: @hanzo/iam PKCE against hanzo.id (VITE_IAM_CLIENT_ID)
- Data: @hanzo/base org-scoped shows / songs / setlist from schema.sql
- Forked from hanzo-starter; identical provider stack, vite.config, deploy contract
2026-07-21 10:39:37 -07:00

29 lines
1.1 KiB
YAML

# Hanzo Cloud build/deploy manifest — hanzo-apps/band-setlist
#
# A forked app is a STATIC SPA: Vite builds `dist/`, Hanzo Cloud serves it at
# `<slug>.hanzo.app` from the project's object-storage prefix (the `*.hanzo.app`
# published-sites edge). There is no server process — identity + data are done
# in the browser (Hanzo IAM PKCE -> IAM token -> Hanzo Base).
build:
runtime: static
install: npm ci
command: npm run build
output: dist
# Serve index.html for client routes (the /auth/callback PKCE return leg).
spa: true
# The Base data plane provisioned on publish. Hanzo Cloud reads this DDL and
# runs `provisionBaseFromDDL` (creates shows / songs / setlist, org-scoped,
# IAM-native).
data:
base: true
schema: schema.sql
# Injected into the build as import.meta.env.* (see .env.example / README).
# The deploy pipeline overrides VITE_HANZO_BASE_URL with the provisioned URL and
# ensures VITE_IAM_CLIENT_ID's IAM client allows this origin's /auth/callback.
env:
VITE_HANZO_IAM_URL: https://hanzo.id
VITE_IAM_CLIENT_ID: hanzo-app
VITE_HANZO_BASE_URL: https://api.hanzo.ai