Web UI control surface for Hero OS VMs: services, AI keys, upgrades, and docs.
- Rust 75.5%
- HTML 24.5%
|
All checks were successful
lab publish / publish (push) Successful in 33m49s
Signed-by: mik-tf <mik-tf@noreply.invalid> |
||
|---|---|---|
| .forgejo/workflows | ||
| crates | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| README.md | ||
| rust-toolchain.toml | ||
hero_cockpit
End-user control surface for a Hero OS Tester Sandbox VM. Lets the user see / start / stop services, set BYO AI keys, trigger upgrades, submit feedback, and read the manual via a simple web UI.
Spec: hero_cockpit#1 — architecture, page inventory, API surface, per-user manifest format. Arc tracker: lhumina_code/home#235 (Hero OS demo-deployer arc).
Workspace shape
Five crates, scaffolded from hero_template:
| Crate | Binary | Socket | Purpose |
|---|---|---|---|
hero_cockpit |
hero_cockpit |
— | Lifecycle CLI (--start / --stop / --info) |
hero_cockpit_server |
hero_cockpit_server |
hero_cockpit/rpc.sock |
OpenRPC backend (service state, BYO keys, upgrade, feedback) |
hero_cockpit_sdk |
(lib) | — | Generated typed client |
hero_cockpit_admin |
hero_cockpit_admin |
hero_cockpit/admin.sock |
Admin dashboard |
hero_cockpit_web |
hero_cockpit_web |
hero_cockpit/web.sock |
End-user web UI |
Quick start
# Build the workspace via lab
lab build hero_cockpit --release --install
# Start the stack via hero_proc
hero_cockpit --start
# Or via lab service
lab service hero_cockpit --install --start
Endpoints
Each daemon serves these:
GET /health— liveness probeGET /.well-known/heroservice.json— service manifest
The server additionally serves POST /rpc (JSON-RPC 2.0 — cockpit.* methods).
Status
- s133: scaffold (5 crates, service.toml × 4 daemons, /health + /.well-known endpoints,
cargo check+lab infocheckclean). The real API surface lands in s134-s139.
License
Apache-2.0