@Johan_Bjorklund wrote:
I have a task called 'move-series' which uses a variable for path, something along the line like
variables: secrets.yml .. .. .. .. move-series: priority: 31 template: - disable-seen-retry - series-metainfo - series-guessit - pushbullet require_field: tvdb_series_name filesystem: path: "/{? folder.root ?}{? folder.torrentseries ?}" recursive: yes retrieve: files regexp: '.*\.(avi|mkv|mp4)$' .. .. ..Along with my variables secrets.yml
folder: root: mnt/mediastorage/ series: TVshows/ movies: Movies/ torrents: .torrents/ torrentmovies: .torrents/movies/ torrentshows: .torrents/shows/Now. When I run this I'd expect it to only look in 'shows' directory, i have a similar task for moving movies which uses almost the same setup, and that one performs its task beutifly. But when I test 'move-series' I see that it also looks at the '.torrent/movies' directory, and if that wasn't enough it actually goes up to my "download-complete" folders as well ('mnt/mediastorage/TVshows/' and 'mnt/mediastorage/Movies/').
When testing my similar task, this does not show the same result.
Also if I write the specific path in plain text, like
path: "/mnt/mediastorage/.torrents/shows/"then it executes as expected.
My question is, what am I doing wrong here? Even though i can solve my issue by "hardcoding" the path, I'd very much want to use the variables option for "purity".
Posts: 1
Participants: 1