This might just be me, but I went through the setup of the Transmission rockon several times because I found the configuration of where things are going to be downloaded to somewhat confusing.
Coming in to it as a user, what you’re shown is the downloads will go to /var/lib/transmission-daemon/[downloads|incomplete]
If you go looking for that path, the transmission-dameon folder doesn’t exist. I sort of understand now that the rockons are being installed using docker, so the paths are in docker containers, not the filesystem as I traditionally think about it.
At first I was trying to figure out how to change /var/lib/transmission-daemon/downloads to the path that I really wanted files to download to. Now I understand that through some backend trickery, this static directory definition points to whatever share you select. Unfortunately that means I can’t select a subfolder of an already existing share.
Additinally, after transmission is installed if I go back to the configuration I have the option to add a share. Here I have a field to fill out the rockon directory. I have no idea what this should be as I suspect this is relative to or chroot’d to a docker container filestructure but I don’t actually know that one way or the other.
Finally, there are some cleanup issues around selecting a share to be used for rockons and then making configuration changes. I’ll open a different thread on that b/c I would consider it an issue or a bug rather than just feedback/thoughts. I’ll link it back here once I’ve made it becuase it’s all related.
EDIT: Here is the link for the cleanup issue. Rockon share cleanup