fn0 / Forte Documentation
Getting Started
- Setup — Prerequisites, installation, environment variables
Forte Framework
Forte is the full-stack web framework built on fn0.
- Quick Reference — Cheat sheet: all handler patterns, naming rules, common snippets
- Overview — Architecture and key packages
- Project Structure — Directory layout and conventions
- Environment Variables — env.yaml, env.local.yaml, secrets, and generated Rust accessors
- CLI Reference — All
fortecommands (including login and cron jobs) - Pages — Page handlers, path/search params, redirects, cookies
- API Endpoints — JSON API handlers under
/api/, no SSR - WebSockets — Inbound routes, outbound routes, singleton connections, streaming sends, graceful disconnects
- Actions & Tasks — Server actions, hooks, queue tasks, admin tasks
- Per-page Head — Per-page
<title>and meta tags viaheadexports - Frontend Runtime —
@forte/reactAPI,__FORTE_BASE_URL__, SSR/hydration lifecycle - SDK Reference —
ForteRequest, HTTP client, cookies, re-exported crates - Serialization —
forte_jsonrules, enum encoding, TypeScript type mapping - Code Generation — How
forte-codegenandforte-rs-to-tswork - Testing —
#[forte_sdk::test], in-memory DB/storage, testing handlers - Troubleshooting — Common build, dev, and deployment issues
doc-db
- Overview — Document database API, transactions,
#[forte_doc]macro
object-storage
- Overview — Per-project S3-style object store, hooks-only credential model
fn0 Platform
- Overview — FaaS runtime, execution model, limits, cluster architecture, worker environment variables for self-hosting
- Limits & Quotas — Per-request runtime limits and fn0 Cloud monthly quotas
- Bring Your Own Cloudflare — How fn0 uses your Cloudflare account for storage, CDN, and custom domains
- Platform Deployment — Deploying the fn0 control plane and worker nodes (maintainers only)
Designs
- Forte WebSockets — Host-owned connection and direct QUIC routing design
- Forte Persistent Outbound WebSockets — Project-scoped singleton connections kept alive by fn0 without an application invocation
- HTTP Body Streaming — 100 MB streaming request and end-to-end response-body contract
Development
- Development Workflow — Code style, testing, build targets, release process