a8aab22163
v1.1.0 PR #0 — SDK Foundation. Lands the architectural shape every v1.1.x stateful service hangs off, without shipping any user-visible service. After this PR, subsequent service PRs (KV v1.1.1, docs v1.1.2, …) are mechanical fill-in: - picloud_shared::{SdkCallCx, Services, ServiceEventEmitter + NoopEventEmitter} lock the per-call context, service bundle, and event-emission trait shape. - executor-core::sdk/ — register_all hook called per invocation; json↔dynamic bridge moved here from engine.rs. - ExecRequest gained app_id, principal, trigger_depth, root_execution_id (the last two reserved for v1.1.1's triggers framework). - orchestrator-core::gate::ExecutionGate — single global semaphore (PICLOUD_MAX_CONCURRENT_EXECUTIONS, default 32). Overflow returns 503 + Retry-After: 1 immediately, no queue. - manager-core::attach_principal_if_present — opportunistic, fail-open middleware wired on data-plane + user-routes. - docs/sdk-shape.md — developer-facing reference for the conventions every future service PR implements against. - Blueprint revisions: Phase 3.5 marked ✓ Shipped, §8.1 KV switched from hstore to JSONB, new §7.5 SDK Architecture section and §7.5.1 trigger sketch, §12 Phase 4 restructured into v1.1.0 → v1.1.8. - CLAUDE.md: current focus → v1.1.0, JSONB note, handle-pattern Working Rule, Runtime Configuration table with the new env var. 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.