bd64a25c97
build_invoke_request already asserts `script.app_id == row.app_id` (dispatcher.rs:752) before constructing an ExecRequest. The queue dispatcher (`dispatch_one_queue`) and the HTTP outbox arm (`build_http_request`) did not. validate_trigger_target blocks cross- app registration at write time, so the gap was latent; but a hand- edited row, a partial backup restore, or a script re-pointed across apps post-hoc could otherwise execute one app's script under another app's SdkCallCx, breaking the cross-app isolation boundary the SDK relies on. Adds the runtime guard at both sites: * dispatch_one_queue — on mismatch, dead-letter the message so the misfire is observable rather than silently dropped, and short- circuit. * build_http_request — on mismatch, return ResolveTrigger error; the outer dispatch arm logs + drops the row (same path as decode failures). Audit ref: security_audit/02_authz_isolation.md (H-F1). 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.