35dbd9f368
Phase 3 foundation (docs §3): env-filtered, proximity-first config inheritance down the group tree. - Migration 0048: `vars` (polymorphic group|app owner via two nullable FKs + CHECK exactly-one, env scope, JSONB value, explicit tombstone) + `apps.environment` (the env marker the resolver filters on — 'an environment is an app'). - config_resolver: a shared chain-walk CTE (mirrors effective_app_role) that walks app → ancestor groups, env-filters in SQL, plus a pure Rust resolution pass implementing the §3 semantics SQL can't — per-key proximity-first, @E-over-* within a level, map deep-merge, tombstone suppression, and provenance for --explain. Verified: 8 unit tests (incl. the §3.2 proximity-beats-env-specificity call, deep-merge, tombstone, boundary) + the candidate-fetch CTE against live Postgres (env-filter drops a non-matching @production value; nearer level shadows farther). 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.