Rust · 0.1.0

Architecture

A Rust process serves the app, API, files and integrations.

Request flow

The production process uses Axum and Tokio. It serves the embedded React/Vite interface, typed Connect RPC, descriptor-driven REST routes, file responses and the /mcp endpoint. REST and Connect operations call the same application implementation. Persistence supports SQLite, PostgreSQL and MySQL; attachments can use database, filesystem or S3-compatible storage.

Startup and shutdown

Startup opens the selected database, applies schema migrations, loads deployment-managed settings, then opens the listener. SIGINT/SIGTERM stops new work and begins graceful shutdown. Database pools, active connections and temporary upload/import sessions have lifecycle handling. Keep your service manager's shutdown allowance consistent with that behavior.

Documentation boundary

The public landing page is a separate static site. It has no application API credentials, database connection or user notes. A website deployment does not update the application process. This documentation explains the source contract, not private hostnames, infrastructure accounts or a claim that every deployment target has passed acceptance tests.