Architecture, deployment,
and runtime maps for the whole platform.

Best when one host can still comfortably own the proxy, services, jobs, and database without becoming a space heater with feelings.

Build once on a dedicated Coolify build server, publish immutable images to the registry, then let the runtime host pull and roll forward.

External load balancer terminates SSL and round-robins to identical servers. Every server runs the same domains and apps behind its own Traefik proxy.

The runtime map of frontends, APIs, backing services, ports, and persistent volumes across the monorepo.

HTTP and WebSocket relationships between frontends, Better Auth, APIs, and the supporting services.

Source-driven Better Auth modules, middleware, and the end-to-end auth request path generated from the auth app.

Shows how a Better Auth JWT moves from the browser into records-service middleware and then into SurrealDB authenticate(token).

The rollout sequencing view that helps explain how migrations, runtimes, and frontends come up without stepping on each other.

A flow-first view of Forgejo, Coolify, the build server, the registry, and the runtime host working in sequence.

Build-once-deploy-everywhere flow with load balancer round-robin and per-server Traefik routing.