Files
mesh-controller/testdata/beside/mesh-catalog/modules/triggerhappy/files/service.conf
T
jschoubben 5ccc87f4d0 Capture mesh-catalog at feat/r4g (2246ccc4) with the templates its manifests name and its predefined.json, and lay the copy out as a repository's root
The catalogue's manifests moved their content into template files and fall back to predefined keys, so a copy of
module.json alone no longer passes the catalogue's own check; the bus's Dockerfile is gone from the catalogue.
2026-10-23 16:24:14 +02:00

9 lines
531 B
Plaintext

# Written by the mesh (module triggerhappy, novox/hq ADR 0212). Replaced on every push.
#
# The daemon opens the input devices as root, then drops to the operator's account with its groups,
# so every trigger runs as the account: it reaches the account's session bus and display, with no su
# and no hard-coded user. Only the mesh's trigger file is read.
[Service]
ExecStart=
ExecStart=/usr/bin/thd --triggers /etc/triggerhappy/triggers.d/mesh.conf --socket /run/thd.socket --user ${machine:account} --deviceglob /dev/input/event*