Files
apress/deploy/uno-q/systemd/zeroclaw-daemon.service
T
Omar SobhandClaude Opus 4.8 89602064c6 feat(deploy): Uno Q workshop-node provisioning kit
Codify the verified board setup into a repeatable kit under deploy/uno-q/:

- config.template.toml — the tested node config: cloud / cloud+fallback /
  on-board-Qwen providers, three agents (default / cloud / local) on the
  hardware risk profile, gateway, peripherals. Secrets stripped; cloud
  endpoint substituted at provision time.
- provision-uno-q.sh — one-shot adb-driven provisioner (no root): install
  config, start llama-server + `zeroclaw daemon`, pair for a bearer token,
  and POST /nodes to APESS.
- systemd/{zeroclaw-llama,zeroclaw-daemon}.service — production units
  (daemon, not `gateway start`, so peripheral tools register).
- README.md — dev (adb) and production (systemd + LAN bind) runbooks.

The individual steps are hardware-verified: all three agent aliases resolve
and route correctly on the board (local→Qwen, cloud→cloud, default→cloud
with Qwen fallback). Full script orchestration + live phone-home land once
the api (with /nodes) is redeployed.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
2026-07-03 06:50:06 -07:00

18 lines
474 B
Desktop File

[Unit]
Description=ZeroClaw daemon (gateway + agent runtime)
After=network.target zeroclaw-llama.service
Wants=zeroclaw-llama.service
[Service]
Type=simple
User=arduino
# Use `daemon`, NOT `gateway start`: only the daemon/agent/channel arms register
# the peripheral tools (uno_q_flash etc.). `gateway start` on an older build
# leaves the agent unable to flash.
ExecStart=/home/arduino/zeroclaw daemon
Restart=on-failure
RestartSec=5
[Install]
WantedBy=multi-user.target