662d5a2cf8
Refactors the bare-metal CLI e2e into focused journey modules sharing one `LazyLock<Fixture>` server (mirrors the dashboard Playwright suite's spawn-once shape), and folds in the comprehensive review-pass fixes on top: * `pic login` is now real auth — username + password POST'd to `/auth/login`. `--token` / `PICLOUD_TOKEN` keep the paste-a-bearer path for CI and API keys. * `pic logout`, `pic apps delete|show`, `pic scripts delete`, `pic api-keys mint|ls|rm`, top-level `pic invoke` / `pic deploy`. * `PICLOUD_URL` / `PICLOUD_TOKEN` override the on-disk creds file globally (gcloud/aws semantics), not just for `pic login`. * Global `--output tsv|json` flag. * `pic scripts ls` (no `--app`) collapses the N+1 per-app walk that aborted on the first 404 into a single `GET /admin/scripts` plus one parallel `apps_list`. Drops the 5× retry the test suite was carrying around it. * HTTP-4xx asserts tightened to specific codes (422/404/403). The old loose `"HTTP 4"` predicates would have masked a regressed 401 from broken auth. * Redundant `tests/integration.rs` deleted — every step it covered lives in one of the focused modules. All endpoints touched on the server side already existed before this branch — no `manager-core` change here. 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.