ae5cf80426
Five dashboard pages (dead-letters, files, users, invitations, queues) reference CSS custom properties like var(--text-muted, #666), var(--bg-secondary, #f5f5f5), var(--border, #e0e0e0), var(--color-link) that the dashboard never defined — so users saw the light-theme fallbacks: #666 text on #f5f5f5 backgrounds, borders that disappeared, a white-on-red error banner. The dashboard otherwise renders with the slate-900 dark palette. Define a :root token set in routes/+layout.svelte using the slate shades already used inline elsewhere. Per-page styles stop hitting their fallbacks; the dark theme renders consistently everywhere. No per-page CSS touched — the tokens cover every fallback already in use (audited via grep across the five pages cited in the AUDIT.md). Adds a few extra tokens (danger/success/warning) so future pages have a single source of truth instead of inline hex. `npm run check` shows no new errors (the pre-existing 149 errors in tests/e2e/* from missing @playwright/test were documented out-of-scope in the AUDIT.md methodology notes). AUDIT.md anchor: F-U-004. 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.