TCP / HTTP API

[trickkiste]

Is there any other way to interface with OBE?
It would be hugely beneficial to have some TCP or REST API to send commands to OBE.

Also it would be nice, if one could start OBE with a config file instead of having to send config commands in via screen, once it is running. This is getting particularly hard, if one decides to run OBE in a docker container!

[gfto]

On 7/25/15 6:20 PM, DI FH Markus Kienast wrote:

Also it would be nice, if one could start OBE with a config file instead of having to send config commands in via screen, once it is running. This is getting particularly hard, if one decides to run OBE in a docker container!

You can use the top three commits in config-file branch:

https://github.com/gfto/obe-rt/tree/config-file

https://github.com/gfto/obe-rt/commits/config-file

[trickkiste]

I am giving it a try right now. If it works fine, I will switch over my Dockerfile to your config-file branch for the time being.

However, I suppose there probably is infrastructure for this in some private OBE branch already, as obe.tv provides a web interface for its commercial product, which needs some way to control the OBE process. @kierank can you shed some light on this?

Regards,
Markus

[trickkiste]

@gfto I have created an OBE docker image based on your patches. Feel free to give them a try. It's a great way to deploy OBE!

https://registry.hub.docker.com/u/trickkiste/obe

[trickkiste]

@gfto, as I don't find no issue tracker on your fork, I have to pose my question here:

Will your fork still send errors to stderr?
And could you include a way to verify, whether the thing came up as expected?
If the commands in the config file and their responses would be output on stdout, that would be very helpful. Currently I can only verify, if things work, by checking CPU utilization or watching the video stream.