Step 10 — Deploy

Option 1 — Static build

For sites without sessions or auth, build a fully static output. Every page is pre-rendered to HTML. Deploy to any CDN: Cloudflare Pages, Netlify, Vercel, S3.

run-what build --path . --output dist

Output is in dist/. All assets are fingerprinted. Upload the directory to your CDN.

Option 2 — Compiled binary

For apps with sessions, database, or auth — compile a single binary. Copy it to any Linux server. No runtime dependencies.

# Build the binary
cargo build --release --bin run-what

# Copy binary + project to your server
scp target/release/run-what user@server:/app/
scp -r site/ components/ what.toml user@server:/app/

# Run it
./run-what dev --path /app --port 8085

Option 3 — Docker

FROM rust:1.75-slim AS builder
WORKDIR /app
COPY . .
RUN cargo build --release --bin run-what

FROM debian:bookworm-slim
WORKDIR /app
COPY --from=builder /app/target/release/run-what .
COPY site/ site/
COPY components/ components/
COPY what.toml .

EXPOSE 8085
CMD ["./run-what", "dev", "--path", ".", "--port", "8085"]

Production databases

SQLite works well for single-server deployments. For scale-out or serverless, switch to Cloudflare D1 or Supabase — same local: query syntax, no code changes.

[database]
type = "d1"
account_id = "..."
database_id = "..."
api_token = "..."

[database]
type = "supabase"
url = "https://xyz.supabase.co"
anon_key = "..."

Deployment via CLI

# Build a static deployment
run-what deploy --target static --output dist

# Generate sitemap.xml
run-what sitemap --host https://yoursite.com

# Run project health checks
run-what doctor