mame_directory is already defined in the template.json, it's used in fetch_local_torrents and update_torrents.
I put my torrents in a 'MAME' subfolder seperate from the other torrents, so I need to set download_dir, otherwise it uses transmission's default directory.
mame_directory is already defined in the template.json, it's used in fetch_local_torrents and update_torrents.
I put my torrents in a 'MAME' subfolder seperate from the other torrents, so I need to set download_dir, otherwise it uses transmission's default directory.
it is the directory the scipt looks in for torrents in fetch_local_torrents, and then again in update_torrents to rename the directory.
I dont understand your request, 'mame_directory' is in config.template.json it is part of the original script
https://djib.fr/djib/PDMameUpdate/src/branch/master/config.template.json
it is the directory the scipt looks in for torrents in fetch_local_torrents, and then again in update_torrents to rename the directory.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
WIP Some suggested 'fixes' for you.
Please provide an updated template.json. Also, could you update the config value to mame-directory with a dash?
mame_directory is already defined in the template.json, it's used in fetch_local_torrents and update_torrents.
I put my torrents in a 'MAME' subfolder seperate from the other torrents, so I need to set download_dir, otherwise it uses transmission's default directory.
Sorry I meant sharing your updated
config.template.jsonin your PR.I dont understand your request, 'mame_directory' is in config.template.json it is part of the original script
https://djib.fr/djib/PDMameUpdate/src/branch/master/config.template.json
it is the directory the scipt looks in for torrents in fetch_local_torrents, and then again in update_torrents to rename the directory.
Well I'll be damned, I totally skipped that. Sorry for the trouble and thanks for contributing.