Skip to main content

Overview

apps/apps serves apps.tuturuuu.com, the central public gateway for routable Tuturuuu web apps. It is a launcher and redirect layer, not a reverse proxy. The gateway exposes app cards for the routable web apps in apps/ and redirects users to each app’s canonical domain:
  • /calendar redirects to calendar.tuturuuu.com
  • /qr redirects to qr.tuturuuu.com
  • /tasks/personal/tasks redirects to tasks.tuturuuu.com/personal/tasks
  • query strings are preserved during redirects
It intentionally excludes infrastructure-only or non-web app directories such as apps/database, apps/mobile, apps/redis, apps/discord, apps/storage-unzip-proxy, and apps/hive-realtime.

Routing Contract

  • /: public app directory.
  • /{appSlug}: redirect to the target app root.
  • /{appSlug}/{path...}: redirect to the same path on the target app.
apps.tuturuuu.com must not own auth callbacks, protected APIs, cross-app token exchange, or app-session cookies. Those flows remain owned by the canonical app or by apps/web for central login. The gateway layout uses @tuturuuu/satellite/providers so the public launcher supports system, light, and dark theme switching through the shared next-themes shell.

Local Development

  • bun dev:apps starts the gateway through Portless.
  • Local app origin: https://apps.tuturuuu.localhost.
  • Direct fallback port: 7818.
The gateway uses hidden locale routing, so old locale-prefixed paths such as /vi/calendar should canonicalize to /calendar while storing NEXT_LOCALE.

CI/CD

Cloudflare qualification, staging and publication use apps-cloudflare.yaml. Previews are Worker versions uploaded at a 0% stage; see the native Start migration runbook.

Validation

Use these focused checks when changing the gateway:
Require the applicable test, type-check, lint and real application build workflows to pass for the exact commit. Follow the repository resource policy for focused local checks; release builds run in CI.

Native renderer verification

The native renderer candidate uses an explicit Start entry. Its request middleware preserves the framework-default CSRF checks for server functions; an empty Start instance suppresses that fallback and must not replace this policy. The entry also lets the owning generator reference its configuration in the typed route footer. Generate route glue through the admitted CI build and retain the authentic supplier bytes. Commit the recovered output, then require fresh clean generation-drift, compiler, behavior and Worker artifact checks. Do not hand-edit generated imports or relax unused-code checks to make a bootstrap artifact pass. Source acceptance and a successful build do not establish canonical traffic or hosted acceptance. The native workflow retains native-emitted-config-apps.json even when emitted configuration qualification fails. The diagnostic records source HEAD separately from the event SHA, hashes and redacted field shapes. It contains no raw config, resource identifiers or secret values and grants no artifact acceptance. Review the actual receipt before changing a strict configuration predicate; retain the source, resource, archive, restore and deployment gates.

Native Worker release identity

On the admitted native Worker, /api/build-info exposes public bundled release metadata (app, full source SHA and environment) before session middleware. It is no-store and accepts GET/HEAD/OPTIONS only; other methods return 405. Other API routes retain their existing authentication/authorization policies. Apps checks its canonical-host fence before this endpoint as well. Legacy Vercel deployments retain their existing behavior until explicit cutover. scripts/ci/wave1-native-publishers.test.js covers path/method/cache behavior; CI original/restored workerd acceptance checks the actual bundled identity. See the native publisher runbook.