a27863d4a6
The `enabled` lifecycle's "a disabled script is not executable via ANY path" guarantee leaked on the queue arm, and the outbox trigger arm lacked the cross-app backstop its siblings carry. - Queue arm: `dispatch_one_queue` bypasses the unified `dispatch_one` fire-time gate, so its only `enabled` guard was the per-tick `list_active_queue_consumers` snapshot — a TOCTOU window for a message claimed in a tick where the script was still enabled. Re-check the freshly-read `script.enabled` before executing and release the claim (`nack`) when disabled; the message stays queued and resumes on re-enable. The nack is load-bearing: `reclaim_visibility_timeouts` only reclaims claims for enabled triggers, so without it the message would sit claimed indefinitely. - Trigger arm: `resolve_trigger` built the ExecRequest with `app_id = row.app_id` while sourcing the body from `trigger.script_id` with no same-app check — the guard the queue/http/invoke arms already have. Add it so a hand-edited/restored row can't run one app's script under another's SdkCallCx. Both regression-locked by new unit tests (full mock harness, verified to fail if the gate is removed): - queue_enabled_gate::disabled_queue_consumer_releases_claim_without_executing - outbox_enabled_gate::disabled_http_outbox_row_is_dropped_without_executing Co-Authored-By: Claude Opus 4.8 (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.