Skip to content

Runtime components and entry points

The declared application runs on AX42. Caddy serves the browser application and routes the public API and Supabase endpoints to their owning processes. The browser application, privileged API and self-hosted Supabase stack have different responsibilities and release evidence. The public marketing website is a separate component.

This reference identifies the declared runtime at the reviewed revision. It does not establish which unit, container image or application revision is running now. Runtime topology explains the application data paths; health signals identifies the observations needed during diagnosis.

Entry point or component Declared service boundary Responsibility and limit
app.toolora.se Caddy, static files under /srv/toolora-app/current Browser assets and public Supabase proxy paths; a loaded page does not prove authenticated queries work
api.toolora.se toolora-api.service, Uvicorn on loopback 8110 Privileged API, portal operations, integrations and process-owned schedulers
Supabase gateway toolora-supabase.service, Kong on loopback 8100 Gateway to Auth, PostgREST, Storage and related stack services; not the privileged business API
Database pooler Declared loopback 5532 Database connectivity for authorized server procedures; not a public browser endpoint
toolora.se and www.toolora.se Separate website on loopback 8120 Marketing website; its availability is not application acceptance
Handbook archive Static HTML and local assets Independent documentation distribution, with no requirement for the application runtime
flowchart LR
Browser[Browser] --> Caddy[Caddy]
Caddy --> App[Static application]
Caddy --> Gateway[Supabase gateway]
Caddy --> API[FastAPI]
Gateway --> Data[Auth, database and Storage]
API --> Data
API --> Jobs[Process-owned schedulers]
Declared application entry points

Ordinary company CRUD can go from browser hooks through PostgREST under RLS. Privileged operations go through FastAPI, which must establish company, capability and resource authority before using privileged access. These two paths share records but do not share an unrestricted permission context. Trust boundaries owns that distinction.

The API process starts its scheduler lifecycle. A responding Uvicorn process can therefore coexist with an unhealthy worker path. A systemd unit marked active only establishes the manager’s process state. Check the expected component configuration and completed-progress heartbeat before treating scheduled work as available.

API releases live under /srv/toolora-api; frontend releases live under /srv/toolora-app. Their current links identify published directories. The installed API unit obtains protected configuration through the component broker before startup, uses the declared runtime user and supplementary groups, and has explicit writable paths. Restart policy and hardening settings do not replace domain authorization.

The configuration reference owns file modes, service credentials and execution identity. Publication owns current-link changes and compatibility checks. Editing a checked-out source file does not update either published component, and observing one component’s SHA says nothing about the other’s release directory.

If a synthetic office user can load the application but cannot read a project, first identify the failing request. A PostgREST denial belongs to identity/RLS/resource scope; an API 503 needs readiness/component evidence; a missing static asset belongs to the frontend release/proxy path. Restarting the API cannot establish that all three cases are repaired.

Record public version observations with time and component. Inspect host state only when the symptom needs it, and keep protected configuration out of terminal output. The source declares a topology; a current observation verifies a particular entry point. Neither proves database migration parity, provider delivery or a complete business journey. Status distinctions explains how to report those facts together.