https://tuturuuu.com/admin by the
tuturuuu-infrastructure Cloudflare Worker behind the apex gateway (binding
MOUNT_ADMIN). The source lives in apps/admin (package @tuturuuu/admin);
the app key, Worker name and legacy host keep infrastructure, and
scripts/app-directories.json maps that key to the directory for CI tooling.
infrastructure.tuturuuu.com answers page navigations with a 301 to
tuturuuu.com/admin.
A checkout that existed before the move can keep an ignored
apps/infrastructure/ directory (usually only node_modules). Delete it with
rm -rf apps/infrastructure before running tests or generators; the docs
inventory generator skips such build-output-only directories, but other tools
may still treat it as an app.
Access
Every page and API keeps the existing gate: the root workspace plus a root admin check (enforceInfrastructureRootWorkspace →
enforceRootWorkspaceAdmin). Pages that need a narrower permission keep that
check as well. The rebuild reuses these checks unchanged and never adds a
fallback page for denied members (they get 404).
Information architecture
Every route keeps its path, so links into
infrastructure.tuturuuu.com/<path>
map one to one onto tuturuuu.com/admin/<path>. Navigation entries live in
src/app/[locale]/(dashboard)/[wsId]/navigation.tsx with aliases, icons and
permissions.
Delivery order
- Mount. Activate the Worker at
/admin: provision its secrets (below), publish the sealed artifact withvoid-cf-publisher.mjs publish --strict, assign it with--expect-current, then add/admin,/admin/*to the gateway’sGATEWAY_MOUNTED_PATHSand theMOUNT_ADMIN → tuturuuu-infrastructureservice binding. Build the gateway version from the deployed one and keep every other mount. Web needsNEXT_PUBLIC_TUTURUUU_ACTIVE_APP_MOUNTS=infrafor direct login returns. - Protection controls. Rate limits and kill switches are rebuilt first, with success and error feedback on every write and end-to-end tests.
- Sections. The remaining sections are rebuilt on the shared
Structureshell and@tuturuuu/uiin the order of the table above. Old code is removed only after the rebuilt section reaches parity. - Redirect.
infrastructure.tuturuuu.comis a Workers Custom Domain oftuturuuu-infrastructure. The production Worker (TUTURUUU_LEGACY_HOST_REDIRECT=1, set by the production config rewrite) answers GET/HEAD page requests with a 301 tohttps://tuturuuu.com/admin<path><query>, with the raw query kept andCache-Control: private, no-store. Machine traffic keeps answering on the subdomain: every/apipath (Cron Control, mobile and desktop deployment bundles, devbox and SDK callers authenticate with bearer credentials that HTTP clients drop on a cross-host redirect) and every other method. Staging artifacts never redirect.
ABUSE_GUARD → tuturuuu-abuse-guard,
entrypoint AbuseGuardEntrypoint) with ABUSE_GUARD_FAMILIES=proxy,ratelimit,integrity
and the Web ABUSE_GUARD_KEY_PEPPER. The guard covers Admin’s proxy traffic
(src/proxy.ts → guardApiProxyRequest), so stopping or resuming the proxy
family applies to Admin as it does to Web; while the family is stopped, Admin
keeps per-instance proxy windows rather than no limit. ratelimit and
integrity are assigned for the shared names only: Admin’s own session and API
limiter (src/lib/rate-limit.ts) stays on Upstash with its in-memory fallback,
and the rate-limit pages read Upstash with SCAN, which the guard store does
not implement. The Protection controls card (Route rate limits, IP blocking) reads and writes
the shared proxy controls through the guard’s proxy view. Web’s API proxy
(/api and /native-integrity/turnstile) reads the same controls, so a switch
changes Web’s API protection as well as Admin’s; document routes and apps that
do not assign the proxy family do not read them.
Mounted apps follow the apex isolation rules: app-owned cookies use
Path=/admin, and no service worker is registered over /.
Worker secrets
Names only. Values are copied from the Vercelinfrastructure project (project
and team-shared variables) or minted for the Worker; nothing is printed or
committed.
Revealing Vercel values can require a step-up
vercel login; a human runs it.
A missing optional secret degrades only its own page (for example, Deployments
reports the coordinator as unavailable).
Smoke checks
/admin response carries the enforced policy
script-src 'self' 'nonce-…' 'strict-dynamic'; object-src 'none'; base-uri 'self'; require-trusted-types-for 'script'; trusted-types default; frame-ancestors 'none'.
The only cookie Admin sets on the mount is NEXT_LOCALE with Path=/admin.
Setting TTR_CSP_ADMIN=report on the Worker moves Trusted Types to a
report-only policy without a rebuild.
Cutover receipt (2026-11-21)
Later Admin versions on 2026-11-21, each assigned with
--expect-current on
the one before it:
The code versions were built on a workstation with the cutover job’s steps: a
clean checkout of the exact SHA, the production Wrangler config rewrite from
the workflow, then seal and pack.
Rollback
- Admin Worker:
void-cf-publisher.mjs assign --version <previous> --expect-current <new>. From5de03f57the chain is681800e7(no guard binding),0aed07f7(Trusted Types report-only) andcea83e5b(code before the Trusted Types fix). - Gateway: redeploy the previous gateway version; removing
/adminentries returns the path to Web. - Redirect: assign the previous Worker version, which serves the app on the subdomain. The custom domain stays on the Worker; it never points back at Vercel.