Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Before auto-name, hardlink, softlink or copy #135

Open
mozartcorleone opened this issue Jul 14, 2021 · 1 comment
Open

[Feature] Before auto-name, hardlink, softlink or copy #135

mozartcorleone opened this issue Jul 14, 2021 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@mozartcorleone
Copy link

It would be a great feature to be able to hard link the content to another folder where it is renamed to the right convention. Many private trackers require the files to be named exactly the same for seeding.

I tried to do this myself but I could not figure out where the renaming process is happening. Would love to know!

@lardbit
Copy link
Owner

lardbit commented Jul 15, 2021

I see your point about seeding. It's beyond the scope of overall simplicity of nefarious, but I'm always open to contributions if someone wants to invest the time. I'm definitely not opposed to the feature, but I try and focus on the general-use stuff.

Here's some of the relevant logic:

Function that returns the new names:

def get_media_new_path_and_name(watch_media, torrent_name: str, is_single_file: bool) -> tuple:

Get the new name:
https://github.com/lardbit/nefarious/blob/master/src/nefarious/tasks.py#L178

Do the rename within transmission:
https://github.com/lardbit/nefarious/blob/master/src/nefarious/tasks.py#L193

@lardbit lardbit added enhancement New feature or request help wanted Extra attention is needed labels Jul 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants