779d906d75
Extends the §11.6 shared-collection machinery to the filesystem-backed `files` blob store (after KV/0053 and docs/0054). - 0055_group_files.sql: widen the group_collections kind CHECK to admit 'files'; add a group-keyed `group_files` metadata table mirroring `files` (0018), CASCADE on group delete. - files_repo: generalize the four path/IO free functions (shard_dir_at / final_path_at / write_atomic_at / read_verify_at) to take an owner-relative dir instead of `app_id`, and make them (plus the cursor helpers) pub(crate). The security-sensitive atomic-write + checksum-on-read mechanics now have a single source shared by the app and group repos. App behavior is unchanged (apps shard at `<app_id>/`). - group_files_repo: FsGroupFilesRepo keyed by group_id, blobs at `<root>/files/groups/<group_id>/<collection>/<id[0:2]>/<id>` — a `groups/` infix disjoint from the per-app subtree, so the existing recursive orphan sweeper covers it with zero change. Schema snapshot blessed (55 migrations); app-files fs tests still green. 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.