Do you think it might be a good idea to move the service-runner from the emonPi repo to the emoncms repo?
The service-runner has no real connection with the “emonPi” per se, it is a service hook for the emoncms application, that preforms other tasks (eg the sync module) that may not be installed to an emonPi or emonSD.
The “emonPi” connection is only that an “update emonPi” specific script can be invoked when a button in emoncms is clicked. That script could actually be anything, a generic updater perhaps, so that all self-hosted users have the option to update via a button on the admin page (for example).
It can still be installed as part of the emonSD image (via the emonPi repo and updater) so emonPi /SD users would not even detect any difference. but much like the mqtt_input or the feedwriter scripts, it should be available to a wider audience. IMO it should be part of emoncms not emonPi.