How do you run qbitmanage via qB's pre-/post-run external program commands for qBittorrent in docker?

[glottisfaun0000]

I know how to exec into the container to install requirements but not how to do it so you don't lose the qbitmanage install whenever the container is recreated. Would you include the requirements install as a custom entrypoint? Or is there a way of putting like a portable install in a directory the container accesses so it's always available? I'm not that experienced with python obviously. Or do you run a parallel qbitmanage container and allow qB to trigger the other container somehow?

Plz share your configuration

[davidgibbons]

I was struggling with this and ended up building a child container that included a webhook: https://github.com/davidgibbons/qbit_webhook

This runs in its own container and then qBitTorrent calls a small curl script to trigger it on torrent start.

[davidgibbons]

Oh yeah, it should totally be hooks.yml and not hook.json based on the default arguments, thats the right place to put it. I'll update the readme, thanks!

- id: qbitmanage
  execute-command: /app/qbit_manage.py
  command-working-directory: /app

[glottisfaun0000]

sweet, works for me now. just to make it clear for anyone else who comes across this, the block starting with - id : qbitmanage should be the contents of a file called hooks.yml in /config as defined for the qbit_webhook container. thanks a lot for sharing this btw, i see no reason this couldn't be wrapped into the main qbit_manage branch!

[glottisfaun0000]

one more thing, does this/could this support the :develop branch of qbit_manage? the image i use is ghcr.io/stuffanthings/qbit_manage:develop so that i have support for qbittorrent 5.0.1

[davidgibbons]

That should be what it's based on. I'm using 5.0.1 as well.
Is it throwing an error that 5.0.1 isn't supported it?

[glottisfaun0000]

just came back to edit and mention it's actually working not throwing an error and I see Version: 4.1.14-develop1 in the output so it works fine and is using :develop. no idea if that's worth adding as an option, thanks 👍