10f76d29ca
- Workspace `1.1.2` → `1.1.3` (`Cargo.toml`). - Dashboard `0.8.0` → `0.9.0` (`package.json`). - CHANGELOG: full v1.1.3 entry covering ScriptKind, ModuleSource, PicloudModuleResolver, the two caches, dep-graph table, route + trigger module rejection, the latent cross-app trigger gap that this release closes, migrations 0015/0016, and downgrade caveats. - Blueprint: mark the "Can scripts `import` Rhai modules?" question as resolved; one-line pointer to the v1.1.3 semantics. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
PiCloud Dashboard
SvelteKit SPA for the PiCloud control plane.
Stack
- SvelteKit 2 with
adapter-static(SPA fallback) - Svelte 5 (runes)
- TypeScript
- Vite
Scripts
npm install
npm run dev # vite dev server on :5173, proxies /api → PICLOUD_API
npm run build # static SPA bundle into ./build/
npm run check # svelte-check
npm run lint
npm run format
By default npm run dev proxies /api/* and /healthz to
http://127.0.0.1:18080. Override with PICLOUD_API=http://host:port npm run dev.
How it fits in
In production Caddy serves the contents of ./build/ as static files and
falls back to index.html for client-side routing. The dashboard only
talks to the control plane (/api/admin/* on the manager); data-plane
invocations go through /api/execute/* on the orchestrator and are not
issued from the dashboard directly during MVP.