Determine appropriate way to include hecate

[Veldhoen]

Hecate is C++ code. I can think of several options to include it in a worker:

• Install everything in one docker. Use Python subprocess to call Hecate executionable from Python (this is roughly the approach (minus containerization) taken in https://github.com/beeldengeluid/dane-shot-detection-worker
• Install Hecate in a separate docker, and use docker-py (or some other approach) to call it from Python
• Use C bindings to run Hecate directly from Python

What is the most elegant way to tackle this problem? @jblom @MartijnBNG @gb-beng any thoughts on this? Did you encounter this before, and how was it solved?

[jblom]

Option 1 was the one I had in mind. Option 3 might be an option as well, but only if Option 1 is not working for some strange reason.

Option 2 I would definitely not use as it goes against the current architecture of having workers that are self-sufficient.

[Veldhoen]

Ok thanks, I'll continue with option 1 and see if we can get everything to work. Using subprocess always feels a bit dirty, but since everything is containerized it's probably not that bad

[jblom]

Option 3 is also fine of course, but using the CLI might be a bit more transparent and easy to debug (also when accessing the container's shell)

[MartijnBNG]

Option 1 is good for me :)