search

filebot / filebot-docker

Docker build files for FileBot
https://hub.docker.com/r/rednoah/filebot/
Apache License 2.0
58 stars 18 forks source link

filebot watcher initial setup #22

Open luciandf opened 6 months ago

luciandf commented 6 months ago

Hello all,

I have added the filebot watcher docker container and i am trying to set it up. I have set the input and output folders and the recursive and the wait environment wariables. What I don't understand for the life of me is how to customize the actual amc script command.

I am running the filebot-node image in parallel and that is working perfectly when I do it manually. What I would like to do is get the command that is running there, and get it to run with the watcher.

I am using portainer for this setup since I don't know much about docker and this makes is easier for me.

Also, just out of curiosity, why isn't there a watch functionality in the filebot-node image? it seems like smomething that would make things so much easier to setup and understand.

rednoah commented 6 months ago

Did you read How do I use the rednoah/filebot:watcher docker container? yet?

The video tutorial will get you started: https://www.youtube.com/watch?v=AjP-ci9Cx5Q

You add amc script options by adding them to the command-line as usual:

$ docker run --rm -it -v $PWD:/volume1 -v data:/data rednoah/filebot:watcher /volume1/input --output /volume1/output

/volume1/input --output /volume1/output are amc script command-line options. You can add more of your own. You can copy & paste from FileBot Node verbatim assuming that the file system view is identical.

I don't use portainer so I can't help you translate the docker command to portainer configuration file. The concepts are exactly the same though, so there should be a configuration field for the command-line arguments.

FileBot Node is primarily made for Synology NAS and QNAP NAS devices, where users can just use scheduled tasks for automation. Adding complex features can be difficult, and comes with a forever-maintenance burden. Support for different CPU / ABI platforms (can't just ship inotifywait), backwards-compatibility with older devices (can't assume recent versions of node), abandoned technology stack (e.g. ExtJS), etc. There's no point in working on it, other than keeping it working at all.