Runtime entry points
The shared application has separate public app and API hosts. Caddy serves the built React application and proxies Supabase paths on the app host. FastAPI serves application routes, MCP and runtime signals on the API host. The table describes the declared runtime contract at the reviewed revision, not a permanent observation of a running deployment.
Address and component mapping
Section titled “Address and component mapping”| Public entry | Declared target | Contract |
|---|---|---|
https://app.toolora.se/ and application deep links |
Static app under /srv/toolora-app/current |
Caddy falls back to index.html; React resolves application routes |
App /auth/v1/ |
Kong at loopback 8100, then GoTrue |
Authentication, token issuance and session endpoints |
App /rest/v1/ |
Kong, then PostgREST | Database API grants, RLS and exposed RPC execution context |
App /storage/v1/ |
Kong, then Storage | Object operations with their own policy |
App /realtime/v1/ |
Kong, then Realtime | Authorized subscription transport |
https://api.toolora.se/api/... |
FastAPI at loopback 8110 |
Registered application routers and route-specific policy |
API /mcp and its discovery documents |
Mounted MCP transport | OAuth-protected tool interface when enabled; separate from /api/mcp-gateway |
API /healthz, /readyz, /version |
FastAPI runtime handlers | Liveness, named readiness dependencies and component build identity |
App /version.json |
Frontend release artifact | Frontend build identity |
toolora.se, www.toolora.se |
Separately declared marketing service at loopback 8120 |
Outside authenticated operational records |
The Caddy template also forwards configured function/GraphQL prefixes to Kong. A forwarded prefix alone does not establish that a corresponding service or public operation is enabled. The Kong configuration is the next source for actual service routes.
Browser and server configuration
Section titled “Browser and server configuration”Frontend configuration initializes Supabase with VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY. BACKEND_URL comes from VITE_BACKEND_URL, defaulting to loopback 8110 for local work. These are built client values; changing a server shell variable does not rewrite a published JavaScript bundle.
Service-role and provider credentials remain in backend runtime configuration. toolora-api.service runs the exact selected release with Uvicorn on loopback. In-process schedulers start through the API lifespan and obey their explicit disable/enable gates. Schedulers owns cadence and worker inventory.
The independent handbook is a separate static artifact. Its Python HTTP-server instructions support distribution without Toolora runtime credentials. The handbook’s local-only browser checks do not imply the product application itself has no external asset or telemetry dependencies.
Version and availability interpretation
Section titled “Version and availability interpretation”/version and /version.json identify different components. The API’s static product-version label is not its full Git SHA. /healthz can pass while /readyz fails a named dependency. Neither endpoint proves business acceptance, current provider data or successful recovery.
Exact-commit deployment uses locks, guarded publication, health checks and retained releases. Schema publication has separate ledger/catalogue and compatibility requirements. An application rollback does not reverse migrations. The operating instructions belong to delivery and docs/DEPLOY.md.
Deep-link example and verification limits
Section titled “Deep-link example and verification limits”A synthetic reader opens /customer/projects/<project-id> on the app host. Caddy returns the React entry rather than looking for a physical file at that path. React establishes the session, and the API separately admits the requested project. A successful static fallback therefore proves routing availability, not project authorization.
Local development uses the repository’s fixed-port Vite contract and local Supabase stack; another hosted preview is not a substitute. A current deployment claim needs fresh public versions and, where relevant, schema and service evidence. This article maps reviewed configuration; it does not certify that every route, provider or component is currently healthy.