start-on-target: uses RSYNC_PREFIX path for config 97/14097/2
authorThierry Bultel <thierry.bultel@iot.bzh>
Fri, 25 May 2018 14:44:29 +0000 (16:44 +0200)
committerThierry Bultel <thierry.bultel@iot.bzh>
Mon, 28 May 2018 11:33:52 +0000 (13:33 +0200)
commit66f7bc88bfc7a17e1ef277c4f7293f95f6ec8b6c
treea2d36605c4aa212c18aef4b838e98962f3b02c93
parente400fb3543217ccd4e2b2a67b018bc947f09bd2c
start-on-target: uses RSYNC_PREFIX path for config

Bindings using the controller need to have a right base
search path for the config files, loaded plugins, and other extra
files (lua, for instance).
Therefore, in the development workflow here, where the binding
is uploaded to the target at a typically unsusual location,
the afb-daemon is given the RSYNC_PREFIX/etc as a base through the
CONFIG_CONTROL_PATH env variable.

Change-Id: Ieb39174918f0d51985e1d63b9f7c6509a05f284a
Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
template.d/start-on-target.sh.in