Tovuk uses a small project contract so humans and agents can deploy without guessing.Documentation Index
Fetch the complete documentation index at: https://docs.tovuk.com/llms.txt
Use this file to discover all available pages before exploring further.
Flow
- Login with GitHub or Google.
- Run
tovuk doctor --json. - Run
tovuk previewfor local verification. - Run
tovuk deploy --wait --json. - Tovuk queues the build, runs checks, and verifies the health route for Rust backends.
- Tovuk exposes the app on a
tovuk.appdeployment hostname.
tovuk deploy from the repo root. The CLI reads the
root tovuk.toml, builds the configured backend and frontend roots, serves the
frontend at /, and routes /api/* to the Rust backend. Use --database to
request managed Postgres for the backend.
Local preview
PORT.
For static frontends, preview builds the frontend and serves the output
directory. For fullstack apps, preview builds both roots, runs the backend, and
serves the frontend with a local /api/* proxy.
Runtime contract
Rust backends must listen on:Managed Postgres
When--database is used, Tovuk injects DATABASE_URL and
TOVUK_DATABASE_URL. It also injects TOVUK_DATABASE_CONNECTION_LIMIT,
TOVUK_POSTGRES_CONNECTION_LIMIT, and TOVUK_POSTGRES_POOL_MODE.
Use the connection limit as the max size of your app’s database pool. This keeps
database work fast and predictable for busy apps while matching the plan limit.