03d03ea6e7
Audit of feat/v1.1.4-http-cron against the v1.1.4 dispatch prompt. All gates green on HEAD; 427 tests pass (+69 new), 140 ignored. SSRF policy audited line-by-line: DNS-rebinding defense via reqwest dns_resolver, literal-IP gap closed at validate_url on every redirect hop, IPv4-mapped IPv6 re-check, IP never leaked in error strings. Cron scheduler's fire-once catch-up policy verified; transactional outbox-insert + last_fired_at bump. Two flagged divergences accepted: three-arg verb(url, body, opts) HTTP shape (resolves a self-contradiction in the brief; body_raw dropped because raw strings just use positional body), and stale schema-snapshot golden re-blessed (pre-existing drift from v1.1.1- v1.1.3 — recommend lifting #[ignore] with CI DB in v1.1.5). Three v1.1.3 follow-ups landed: module backend error redaction, rhai = "=1.24" exact pin, retroactive CHANGELOG security note.
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.