Skip to content

0.1.3: the system, site and talkgroup in a script's environment - #1

Merged
robotastic merged 1 commit into
mainfrom
sites
Oct 17, 2026
Merged

robotastic merged 1 commit into
mainfrom
sites

Conversation

@robotastic

Copy link
Copy Markdown
Contributor

Trunk Recorder Pro now has systems with sites (TrunkRecorder/trunk-recorder-pro#51; SDK trunk-recorder-plugin 0.4.0). A call heard on several sites is saved once, in the system's folder. short_name is the system, and the call JSON says which site the call was kept from (site). The per-system Script setting is now per system, not per site.

The problem: a script that told sites apart by their short name or folder (each was a system in Trunk Recorder) can no longer do that.

What changes

  • Environment: every run gets SHORT_NAME, SITE and TALKGROUP, the same values as in the call JSON. Arguments are unchanged, so existing scripts still work.
  • Docs: the README covers the new variables and Trunk Recorder's multiSite.
  • Versions: built with trunk-recorder-plugin 0.4.0; version 0.1.3.

Tests: new test the_system_site_and_talkgroup_in_its_environment. All 10 tests pass, and clippy and cargo fmt --check are clean.

Release after merge: tag v0.1.3, then a registry PR.

🤖 Generated with Claude Code

Trunk Recorder Pro's systems now have sites (trunk-recorder-plugin 0.4.0):
a call heard on several is saved once, in the system's folder, its JSON
saying the site it was kept from. Scripts get SHORT_NAME, SITE and
TALKGROUP in their environment, so one that told sites apart by their
short name or folder can still do it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@robotastic
robotastic merged commit 2d81a50 into main Oct 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant