From 207bff9cb9773e3e0ef7fe7114e4b1aa70ffd4b6 Mon Sep 17 00:00:00 2001 From: Luke Hoersten Date: Tue, 28 Jul 2026 21:11:08 -0500 Subject: Rename mattertimesync role to mattertimectl (build + controller) - Rename role dir and all vars from mattertimesync to mattertimectl - Rename the server subrole to controller - Build via cargo instead of npm; run the binary directly (no node) - Default fabricLabel to "Matter Time Controller" --- mattertimectl/build/defaults/main.yaml | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 mattertimectl/build/defaults/main.yaml (limited to 'mattertimectl/build/defaults') diff --git a/mattertimectl/build/defaults/main.yaml b/mattertimectl/build/defaults/main.yaml new file mode 100644 index 0000000..56cabdc --- /dev/null +++ b/mattertimectl/build/defaults/main.yaml @@ -0,0 +1,16 @@ +--- + +mattertimectl_version: "0.1.0" +# https://github.com/lukehoersten/mattertimectl/tags +# Rust project: cargo build --release produces one self-contained binary +# (all runtime deps are pure Rust), so the target only needs the binary to +# run it. The source tarball must point at the Rust implementation. +mattertimectl_tar: "https://github.com/{{github_user}}/mattertimectl/archive/refs/tags/v{{mattertimectl_version}}.tar.gz" +mattertimectl_build_dir: "{{build_work_dir}}/mattertimectl-{{mattertimectl_version}}" +mattertimectl_srv_dir: "{{build_srv_dir}}" + +# Keep cargo's registry cache, the rustup toolchains, and the build output +# on build_work_dir (the SSD), not the SD card. +mattertimectl_cargo_home: "{{build_work_dir}}/.cargo" +mattertimectl_rustup_home: "{{build_work_dir}}/.rustup" +mattertimectl_cargo_target_dir: "{{build_work_dir}}/.cargo-target" -- cgit v1.2.3