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>

diff --git a/template.d/start-on-target.sh.in b/template.d/start-on-target.sh.in
index 9baab37..ae28506 100755 (executable)
--- a/template.d/start-on-target.sh.in
+++ b/template.d/start-on-target.sh.in
@@ -14,7 +14,17 @@ export AFB_REMPORT=@AFB_REMPORT@
 export AFB_TOKEN=@AFB_TOKEN@
 
 exec ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -tt $RSYNC_TARGET << EOF
-    afb-daemon --workdir=$RSYNC_PREFIX --monitoring --port=$AFB_REMPORT --roothttp=./htdocs --ldpath=./lib --verbose --token=$AFB_TOKEN &
+    CONTROL_CONFIG_PATH=$RSYNC_PREFIX/etc \
+    afb-daemon \
+       --workdir=$RSYNC_PREFIX \
+       --monitoring \
+       --port=$AFB_REMPORT \
+       --roothttp=./htdocs \
+       --ldpaths=./lib \
+       --verbose \
+       --token=$AFB_TOKEN \
+       --name $PROJECT_NAME &
+
     PID_DAEMON=\$!
     trap "echo REMOTE-SIGNAL TRAP; kill -15 \$PID_DAEMON" INT QUIT TERM EXIT
     echo "Target Process Waiting for command"