I see, it's becoming more clear now.
So i need to remove the ":xpra" from the docker in order to pass all those command line arguments. Once passed, I can then run the XPRA version with the customizations that have already been baked in.

Appreciate the clarification.

You can set your custom settings in the GUI, so I would recommend just using the GUI: right, I know I *can*, but a lot of the documentation that is around surrounds passing command line arguments via the fn:properties. And I can't find a single example of how to pass ANY other filebot command line ...

Thank you! You are much more knowledgeable than I am on both docker and filebot. I appreciate you pointing me in the right direction. Regarding the other thread about xttr attributes, I looked through my logs going back a few years (now that I know where they are) and I've been getting those errors ...

Been making progress. I got the port sorted. Had to actually look at the xpra file in github to find real documentation on the arguments accepted. https://github.com/filebot/filebot-docker/blob/master/Dockerfile.xpra Here is my current docker run command. docker run --restart unless-stopped --name ...

:arrow: If your Ubuntu is a headless Ubuntu Server, then I strongly recommend using the FileBot Desktop application from your Desktop, mount the remote file system via SMB / NFS / SSHFS / WebDAV / etc, and then move / rename files as usual. because windows SMB/CIFS doesn't support hardlinks ...

(zenity:488): GVFS-RemoteVolumeMonitor-WARNING **: 02:59:19.406: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported Gtk-Message: 02:59:19.608: GtkDialog mapped without a transient parent. This is discouraged. 1 file linked. Failed to write xattr key: net.filebot ...

docker run --log-driver local --log-opt max-size=20m --rm -it -v data:/data -v /mnt/media:/mnt/media -p 5454:5454 --env XPRA_AUTH="password:value=testing" rednoah/filebot:xpra --def net.filebot.theme=FlatLight I'm trying to do a few things with the docker-xpra and finding it frustration because of ...

So filebot node appears very poorly documented in general, especially around how to get it going on if you don't have a synology or using docker.
Does anyone have any documentation I can read on how to get filebot node installed and useable on base ubuntu rather than inside docker?

Not possible, torrents don't work that way. Changing the filenames is changing the data, breaking your torrent. You're making your copies different to those that are in the swarm. Symlinks or hardlinks solve this problem. sigh, that's just not true at all. I solved my issue. I just switched to ...

Transmsission (while in some way is the best torrent client) frustratingly lacks the ability to have more than one default download directory. If you don't want everything dumped in one directory, you have to set the destination per torrent, every time you add one. I do want everything dumped into ...

I am 100% new to automating filebot. I have an ubuntu VM that I run transmission-daemon. I use transmission GUI. Step 1: I download a torrent, and transmission downloads it to to /mnt/media/downloads/incomplete Step 2: when the file(s)/folder(s) are done, transmission moves it to /mnt/media ...

then how do I modify the existing script to add the code back in that gets the feature back?
I don't have enough knowledge about filebot scripts to make something dedicated.

correct, all available posters for the same movie.

script =
.\filebot.exe -script fn:artwork.tmdb <path to movies>

The problem is, the script is only downloading the 'first' movie poster available instead of ALL of the available movie posters.
How do I get filebot to download more than just the first available movie poster?