mirror of
https://github.com/hanzoai/id.git
synced 2026-10-16 18:38:15 +00:00
Replaces the Cloudflare Worker (hanzo.id-worker) and the Next.js portal
with a pnpm monorepo following the a-monorepo/id pattern.
Layout:
apps/web/ Vite + React 19 SPA, embeds @hanzo/gui shell
k8s/ Deployment(2) + Service + Ingress (4 hosts, 4 TLS)
pkgs/shared/ @hanzo/id-shared — TenantConfig, resolveTenant,
loadBrand (browser + node)
pkgs/auth/ @hanzo/id-auth — AuthClient (wraps @hanzo/iam REST)
+ LoginForm/SignupForm/ForgotForm/OTPForm
pkgs/idv/ @hanzo/id-idv — pluggable IDV (stub, persona,
onfido, veriff) behind one
IDVProvider interface
legacy-nextjs/ Frozen — Next.js predecessor. Delete after v0.1.0 ships.
Dockerfile Two-stage: pnpm build → hanzoai/static:0.4.1 serves /spa
README.md
LLM.md Architecture, dev, deploy, cutover plan
Tenant resolution: hostname → TenantConfig (orgId, iamUrl, clientId,
appName, publicOrigin, brandPackage). Built-in defaults for
hanzo.id/lux.id/zoo.id/pars.id; runtime override via
IAM_TENANT_CONFIG_JSON env (served as /config.json at pod startup).
Brand resolution: each per-org brand pkg (@hanzo/brand, @luxfi/brand,
@zooai/brand, @parsdao/brand) ships brand.json. The Vite plugin
brandJsonPlugin emits /brand/<pkg>/brand.json verbatim; the browser
fetches the right one based on the resolved tenant. No bundle bloat.
IDV: stub (default for dev), persona, onfido, veriff. Each adapter
implements `IDVProvider` from pkgs/idv/src/provider.ts. Swap providers
with one registration call at boot — portal code unchanged.
Cutover (separate ops PR — not in this commit):
1. Tag + push image ghcr.io/hanzoai/id:0.1.0
2. Apply k8s manifests, cert-manager issues TLS
3. Remove CF Worker routes for hanzo.id/lux.id/zoo.id/pars.id
4. CF A records → 129.212.164.5 (hanzo ingress LB)
5. Archive hanzo.id-worker repo
32 lines
1.1 KiB
JavaScript
32 lines
1.1 KiB
JavaScript
/**
|
|
* Workaround for @cloudflare/next-on-pages + Next.js 15
|
|
*
|
|
* Next.js 15 generates /_not-found as a Node.js function even when
|
|
* the root layout exports `runtime = 'edge'`. This script removes
|
|
* the _not-found function and its route from the Vercel build output
|
|
* so next-on-pages can proceed. The middleware handles 404s anyway.
|
|
*/
|
|
|
|
import { rmSync, readFileSync, writeFileSync } from 'fs'
|
|
import { join } from 'path'
|
|
|
|
const outDir = join(process.cwd(), '.vercel', 'output')
|
|
const funcDir = join(outDir, 'functions')
|
|
|
|
// Remove _not-found function directories
|
|
for (const name of ['_not-found.func', '_not-found.rsc.func']) {
|
|
try {
|
|
rmSync(join(funcDir, name), { recursive: true, force: true })
|
|
console.log(`Removed ${name}`)
|
|
} catch {}
|
|
}
|
|
|
|
// Remove _not-found route from config.json
|
|
const configPath = join(outDir, 'config.json')
|
|
const config = JSON.parse(readFileSync(configPath, 'utf8'))
|
|
config.routes = (config.routes || []).filter(
|
|
(r) => !String(r.dest || '').includes('/_not-found')
|
|
)
|
|
writeFileSync(configPath, JSON.stringify(config, null, 2))
|
|
console.log('Patched config.json — removed _not-found routes')
|