How vu-ase/rover works
Project type and purpose
• This is a distributed, full-stack “Rover Control” system comprised of three coordinated pieces:
• roverd – a Rust-based daemon running on the Rover hardware that schedules and executes pipelines and services via a REST API (per the OpenAPI spec in spec/api).
• roverctl – a Go CLI tool that talks to roverd’s REST API and also runs a local proxy (WebRTC/WebSocket) to forward browser traffic.
• roverctl-web – a SvelteKit web frontend that uses a generated TypeScript client against the OpenAPI spec, connecting through the roverctl proxy for live control and monitoring.
File structure
• Top-level: three component roots (roverd/, roverctl/, roverctl-web/), a shared spec/ folder for API and configuration schemas, manage/ scripts for batch operations, and .github/ CI.
• Each of the three components has its own Dockerfile and devcontainer for isolated development.
• OpenAPI codegen artifacts under both roverd/openapi and roverctl-web/src/lib/openapi.
Relationships & data flows
• User types CLI commands → roverctl → HTTP → roverd
• Browser connects to roverctl’s WebRTC proxy → WebSocket → roverctl → HTTP → roverd
• OpenAPI spec (spec/api/schema.yaml) is the single source of truth → codegen → roverd/openapi & roverctl-web/src/lib/openapi
Architectural patterns & design principles
• Separation of Concerns: Edge service (roverd), local control/proxy (roverctl), browser UI (roverctl-web)
• Contract-First: OpenAPI-driven API design and client generation
• Proxy Pattern: roverctl serves as an HTTP↔WebRTC bridge for secure, debuggable remote access
• State Machine: roverd’s internal pipeline scheduler follows a well-defined state machine
Technologies & frameworks
• roverd: Rust, Tokio/async HTTP framework, OpenAPI codegen, state machine module
• roverctl: Go, Cobra CLI, net/http, Pion WebRTC or similar
• roverctl-web: SvelteKit, Vite, TypeScript, OpenAPI generator, Tailwind CSS