7d3ced0776
CHANGELOG.md: new v1.1.9 entry above v1.1.8 — covers queue::* SDK, queue:receive trigger kind, dispatcher queue arm + visibility-timeout reclaim, invoke() + invoke_async(), retry:: SDK (including the retry::run rename deviation), admin HTTP endpoints, dashboard 0.15.0, Services::new + Limits + Engine + register_all signature changes, migrations 0034/0035, F1-F5 follow-ups, env vars + SDK schema bump. No upgrade-order constraint (pure additive). HANDBACK.md: replaces v1.1.8's at repo root. 12 sections per the brief: 1. Scope coverage table — 21 line items, all ✅ 2. Queue dispatcher design (claim SQL, ack/nack/dead-letter, reclaim) 3. invoke() re-entrancy (Engine self_weak, fresh SdkCallCx, cross-app guard, depth bound) 4. retry::* (closure passing, sleep mechanics, clamping, jitter) 5. Dashboard notes 6. F1-F5 implementation per follow-up 7. Deviations beyond the brief — 7 numbered: D1: retry::with → retry::run (both with/call are Rhai reserved) D2: Trait move skipped (Engine in scope, AST cache loss deferred) D3: Retry columns on parent only (avoids duplicating source of truth) D4: Limits::trigger_depth_max mirrored from TriggerConfig D5: One-consumer-per-queue via pg_advisory_xact_lock D6: invoke() exposed globally (not invoke::*) D7: invoke_async runs once 8. Verification with LITERAL output (fmt + clippy + test totals) 9. Open questions for the reviewer (4) 10. Latent findings (lints surfaced + fixed; no carry-forward from main) 11. Deferred items (nothing slipped; standing v1.2+ list) 12. Known limitations (closures across invoke, in-process only, etc.) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
PiCloud
A lightweight, self-hosted, event-driven serverless compute platform. Upload a Rhai script, get an HTTP endpoint. Designed to run on a single modest server with no idle CPU cost, and to scale out to a small cluster when you need it.
Status: Phase 1 — MVP scaffolding in progress.
The authoritative design lives in
serverless_cloud_blueprint.md.
Why
Existing serverless platforms are either cloud-locked, heavyweight, or both. PiCloud aims for the opposite end of the spectrum: one binary, one database, one reverse proxy — running on hardware you already own.
Architecture (one paragraph)
PiCloud splits into three logical services — manager (control plane: scripts, schedules, dashboard), orchestrator (per-node event ingress and dispatch), and executor (per-node Rhai sandbox) — each backed by a *-core Rust library. In MVP they run in a single process; in cluster mode they run as three binaries with one manager and one orchestrator + executor per node. Caddy fronts everything; PostgreSQL is the single source of truth.
See CLAUDE.md for working notes and serverless_cloud_blueprint.md for the full design.
Quick Start
Coming as scaffolding lands. For now:
# Rust toolchain (pinned via rust-toolchain.toml)
cargo check --workspace
# Run the all-in-one MVP binary (once main.rs is wired up)
cargo run -p picloud
Repository Layout
crates/
shared/ cross-cutting types
executor-core/ Rhai engine + sandbox
orchestrator-core/ event ingress, dispatch
manager-core/ control plane
picloud/ MVP all-in-one binary
picloud-{manager,orchestrator,executor}/ cluster-mode binaries (skeleton)
dashboard/ SvelteKit
caddy/ Caddyfile
docker/ Dockerfiles
docs/
git-workflow.md Trunk-based workflow
Contributing
See docs/git-workflow.md for the branching and commit conventions. TL;DR: trunk-based, short-lived branches, Conventional Commits, no force-pushing main.
License
TBD.