700ae7b7d1
/admin/users is the owner+admin surface for managing the platform's user list. Members get bounced to /profile?denied=users. Invite generates a random 16-char password client-side, POSTs the new user, and surfaces the cleartext exactly once in a yellow- bordered reveal modal with a Copy button and an "I've shared it" acknowledgement gate. Owner role is intentionally not in the create form — promote via Edit after creation, matching the backend's deliberate-step comment. Edit handles username, email, role (with affordance hiding: admins see admin/member only), is_active toggle, and a separate "Reset password" button that re-uses the same reveal flow. Delete uses ConfirmModal with confirmPhrase=username and explains the last-owner/last-admin 422s up front. Username + email validated client-side against the same patterns the backend enforces so the form fails fast rather than always on the round-trip. 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.