d064681c49
Audit of feat/v1.1.5-files-pubsub against the v1.1.5 dispatch prompt. All gates green on HEAD; 491 tests pass (+64 new), 139 ignored. Atomic write protocol audited line-by-line: single-pass SHA-256, temp→fsync→rename→fsync-dir→DB sequence as specified, unique pid+ counter temp suffix, path-traversal defense at SDK boundary and repo. Pub/sub fan-out is correctly transactional (single tx begin+commit; one outbox row per matching subscriber; trigger_depth saturating- bumped). Topic pattern matcher rejects every shape the brief called out (*.created, **, a.*.b, user.*x, *user, empty). Three flagged open questions resolved: orphan-sweep deferred (matches planning decision), test count 63 vs 70 (defensible — gap is the dispatcher e2e test, which is already covered for kv/docs/cron via the shared dispatcher path), empty-blob = missing-data (defensible interpretation, relaxable later). First CI workflow added; schema_snapshot un-ignored with DATABASE_URL- absent skip path.
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.