35345e62de
Exports a group as a [group] manifest: its scripts, [[routes]]/[[triggers.*]] TEMPLATES (with the group-only sealed/shared flags), a shared collections entry, [vars]/[secrets], extension_points, and [suppress]. Groups own no workflows. The group trigger/route reports were display-only (no ops, dispatch, retry, host_kind, cron tz, queue timeout) so a pulled manifest could not re-plan clean. Enriched TriggerTemplateInfo with the full internally-tagged TriggerDetails JSON + dispatch_mode + retry_max_attempts, and RouteTemplateInfo with raw manifest-shaped fields (method/host_kind/host/host_param_name/ path_kind/dispatch_mode); pic routes ls --group now applies the ANY/host munge client-side, consistent with the app pic routes ls. pull.rs factors the script-writing + trigger-decoding it shares with the app path. Pinned by a pull journey: a group with a sealed+shared kv trigger, a sealed route, a shared collection, and a var round-trips and the exported manifest re-applies clean. 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.