6449cb6f6a
apps/[slug]/users/+page.svelte: list, create form, edit modal, revoke-sessions, reset-password (returns one-shot token in a copy modal so the admin can paste it into a manual reset link), delete. apps/[slug]/users/invitations/+page.svelte: pending list, create form (with optional inline email template — off by default for out-of-band delivery), revoke. Tab strip in apps/[slug]/+page.svelte gets a Users entry above Files, matching the external-route pattern files/ and dead-letters/ already use. Sub-tab navigation from Users -> Invitations and back. api.ts gains AppUser / Invitation / ResetPasswordResponse / CreateAppUserInput / PatchAppUserInput / InvitationTemplate / CreateInvitationInput types and `users` + `appInvitations` namespaces mirroring the appMembers shape. svelte-check is green on every file under src/. The 150 errors the runner reports are all pre-existing in tests/e2e/ (missing @playwright/test install — unrelated to v1.1.8 changes). 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.