blob: fc3548bcf25694b0b419aca0eb559a0b1f7632e6 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
WARNING: controller is now independent from AAAA and thus should be imported by your binder before requesting it.
For this your only have to provide the path where to find your controller you are in your development tree probably with something
like --binding=../../afb-controller/build/ctl-binding/afb-controller.so on the other hand if you controller was installed you
should import it from where ever you install it.
To run this controller sample from your developpement environement use
```
export BUILD_DIR=build
# with an internal MPDC (Pusic Player Daemon Client) API
afb-daemon --port=1234 --workdir=. --roothttp=../htdocs --token= --verbose \
--alias=/monitoring:$HOME/opt/afb-monitoring \
--ldpaths=package/lib \
--alias=/monitoring:/home/fulup/opt/afb-monitoring \
--binding=../../afb-controller/$BUILD_DIR/package/lib/afb-controller.so \
--binding=../../afb-mpdc/$BUILD_DIR/package/lib/afb-mpdc-api.so \
--ws-server=unix:/var/tmp/afb-ws/mpdc
# with an exernal MPDC API
afb-daemon --port=1234 --workdir=. --roothttp=../htdocs --token= --verbose \
--alias=/monitoring:$HOME/opt/afb-monitoring \
--ldpaths=. \
--alias=/monitoring:/home/fulup/opt/afb-monitoring \
--binding=../../afb-controller/$BUILD_DIR/ctl-binding/afb-controller.so \
--ws-client=unix:/var/tmp/afb-ws/mpdc
# Note:
- Both sample make the assumption the monitoring HTML5 app is avaliable at $HOME/opt/afb-monitoring
- With second sample you should obviously have your MPDC service exposing its API with --ws-server=unix:/var/tmp/afb-ws/mpdc
- Should use 'make populate' to get ./build/package/lib to be uptodate
```
Running AAAA from you IDE 
|
