19f3647f0e
Postgres-backed integration tests surfaced two assertion fixes while verifying the audit branch: * email_inbound::create_without_inbound_secret_is_rejected (added in the H-B2 commit) asserted 400; TriggersApiError::Invalid maps to 422 (UNPROCESSABLE_ENTITY). Corrected. * api::version_includes_public_base_url had two rotted assertions — `schema` pinned at 6 (it's migrations::latest_version(), which had climbed to 41 and is now 42 after 0042_secrets_envelope_version.sql) and `sdk` pinned at "1.1" (the crate is at "1.10"). The test is #[ignore]-gated so the rot went unnoticed in normal runs. Both pinned to current reality. These were pre-existing failures, not caused by the security changes. Verified against a throwaway Postgres: schema_snapshot, api (53), authz (28 of 29 — see below), dispatcher_e2e, email_inbound, invoke_e2e, queue_e2e all green. Known pre-existing failure (NOT fixed here, out of Tier 1+2 scope): authz::deactivating_user_revokes_their_api_keys fails identically on the pre-branch merge-base. It's the PrincipalCache revocation-lag Medium the audit flagged as unfixed (resolve_principal caches by token-hash with no eviction on deactivation; lag bounded by the 60s TTL). Deferred to a Tier 3/4 pass. 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.