72802de644
The runtime heart: a descendant app's event now fires its ancestor groups' trigger templates, resolved LIVE (no materialization). - trigger_repo: list_matching_kv/docs/files prepend CHAIN_LEVELS_CTE and `JOIN chain c ON (t.app_id = c.app_owner OR t.group_id = c.group_owner)` (bind $1 = app_id), so each returns the app's own triggers PLUS ancestor-group templates in one statement. NULL-comparison semantics keep app/group rows from cross-matching; each row matches at exactly one chain depth (no dup fan-out). - pubsub_repo: same union on the publish fan-out query. - The outbox row stamps the firing app_id + the (group-owned) script_id; the dispatcher's existing script_invocable() (app-owned OR invocable via chain membership) already runs a group handler under a descendant app — the Phase-4 inheriting-app boundary, unchanged. Glob/ops/topic filtering in Rust is untouched. 404 manager-core unit tests green; clippy -D clean. Cross-subtree firing is journey-proven in T4. 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.