The transmissionvpn docker image assumes that you have mounted a volume to /data, and sets a lot of defaults based on that, such as the default download dir, incomplete downloads dir, and watch dir.
When I installed transmissionvpn this data volume was not configured. This meant that docker generated the volume automatically and transmission used that dir rather than downloading to the created torrents folders.
I added a mount point pointing data (in the container) to {{ downloads.torrents }}/transmissionvpn (on the disk).
How Has This Been Tested?
Ran it locally and verified in portainer that it was being mounted correctly:
I wasn't sure how to test it in the case that torrents_download_path doesn't exist and would appreciate any input you have on whether my code looks correct
I don't think you really need to account for the case where torrents_download_path doesn't exist since that's a pretty pathological case that would involve someone changing another role.
Description
The transmissionvpn docker image assumes that you have mounted a volume to /data, and sets a lot of defaults based on that, such as the default download dir, incomplete downloads dir, and watch dir. When I installed transmissionvpn this data volume was not configured. This meant that docker generated the volume automatically and transmission used that dir rather than downloading to the created torrents folders.
I added a mount point pointing
data
(in the container) to{{ downloads.torrents }}/transmissionvpn
(on the disk).How Has This Been Tested?
Ran it locally and verified in portainer that it was being mounted correctly:
I wasn't sure how to test it in the case that
torrents_download_path
doesn't exist and would appreciate any input you have on whether my code looks correct