search

JohnDoee / autotorrent2

Cross-seed matching and torrent lifecycle tool
https://johndoee.github.io/autotorrent2/
MIT License
151 stars 12 forks source link

Merge in rtorrent client_path fix #13

Open newadventure079 opened 2 years ago

newadventure079 commented 2 years ago

Merge in https://github.com/TiarnanRedmond/autotorrent/pull/1/files

JohnDoee commented 2 years ago

I originally thought it was mostly putting rtorrent .torrent file in a specific location but it seems like it is designed to align paths in regards to e.g. docker?

newadventure079 commented 2 years ago

Yes, I believe so. If you look at the issues in the at1 repo, docker paths caused a lot of headaches.

https://github.com/JohnDoee/autotorrent/pull/54

https://github.com/JohnDoee/autotorrent/issues/33

JohnDoee commented 2 years ago

In these situations, do you align the data path so soft links will work or do you use hard links ?

The question is if it should be a dual-option type of things where you do e.g.

rewrite_mapping = [
  ["/mnt/data", "/inside/docker/data"],
  ["/mnt/storepath" "/inside/docker/storepath"]
]

and it'll just rewrite the paths for links and everything so they match inside the container.

newadventure079 commented 2 years ago

I've always used soft

JohnDoee commented 2 years ago

So you align the data path but not the store path? Is there a reason for that now autotorrent has dynamic store paths?

newadventure079 commented 2 years ago

It was just confusing b/c I was using it in docker and I didn't realize the paths weren't lining up. You can see others had issues too. It's not a big deal for me now that I've solved it but I went months w/o getting at1 to work. I'm sure the same issue with come up again soon