v0.1.0 — Dashboard-only device build (unverified)
Pre-releaseCardMesh v0.1.0 — Dashboard-only, release candidate
docs/DEVICE_BUILD.md before submitting it anywhere — it lists every assumption this build makes and exactly what to try if it doesn't run.
What's in cardmesh_0.1.0_arm64.deb
A self-contained package: a real aarch64 Linux ELF binary (cross-compiled with zig cc against a Debian bookworm sysroot) plus all 29 of its transitive runtime shared-library dependencies, bundled under /usr/lib/cardmesh and SONAME-verified. Only libc6 is required from the target system.
sudo dpkg -i cardmesh_0.1.0_arm64.deb
What's implemented
- Dashboard screen only (per the README's Dashboard mock): source name, node/active/channel/unread counts, connection status.
- A background thread polls MeshMonitor every 10s so the UI never blocks on network I/O.
- Global shortcuts:
Rrefresh,Q/Escquit. - Reads
~/.config/cardmesh/config.json— there is no first-run setup UI yet, so this file must exist before launch (see README for the format).
What's NOT implemented yet
Channels, Chat, Nodes, Node Details, Direct Messages, Sources, Telemetry, Traceroute, Field Mode, Settings screens; first-run setup UI; local SQLite caching is wired into storage but not yet used by the device UI.
Known unverified assumptions (see DEVICE_BUILD.md for details)
- Framebuffer device path (
/dev/fb0, override viaCARDMESH_FB_DEVICE) - Input device path (
/dev/input/event0, override viaCARDMESH_INPUT_DEVICE) - Display color depth (16bpp/RGB565 assumed)
- Target glibc ≥ 2.36 (Debian bookworm baseline — bundled libs will fail to load on an older glibc)
- Whether the online emulator even runs a plain Linux fbdev/evdev binary, vs. requiring AppBuilder-specific integration
Also new in this release
Community health files: CODE_OF_CONDUCT.md, CONTRIBUTING.md, LICENSE (MIT), SECURITY.md.
The host-testable core (HTTP client, MeshMonitor API client, models, config, SQLite storage — no CardputerZero hardware needed) builds and passes its full test suite via cmake + ctest; see the main README.