-
-
Notifications
You must be signed in to change notification settings - Fork 114
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
Move download directory configuration to .rtorrent.rc #181
base: master
Are you sure you want to change the base?
Conversation
👍 this would have come in very handy for me today, and you can't just copy it in so i had to just hide the real paths from the container in the end |
It will break init scripts and configuration if changed to smth else:
docker-rtorrent-rutorrent/rootfs/etc/cont-init.d/03-config.sh Lines 147 to 148 in c99391c
|
Why is it set up like this? And not the same as well described in the link above. Many of your potential user bases are using Sonarr, Radarr, (etc)rr. I agree with K44sh which has forked this repo and made the necessary edits. |
I have made my own custom version of the image where the downloads are saved to location |
Thanks @XxAcielxX, I was getting mad trying to configure rtorrent for the simplest use case possible (manually pick a download folder and download the files exactly there), but failed to do so. Switched to your image and it worked like a charm! |
This addresses the issue of download paths not being easily configurable (#105, #7, #44, #57).
As @crazy-max said in his comment on #105 the conventional solution here is to use bind-mounts rather than changing directories in-solution.
@hollanbm, however, raised an important scenario in which that is not applicable. If this container needs to communicate paths to external services, simply using a bind mount is not a viable solution. One might think it's just easy enough to add the
/downloads
mount on any other container that needs access to the path, but this breaks hardlinking. A file can't be hardlinked across bind mounts. As such, the only solution is to change the paths in the configuration file.This PR simply moves the configuration of download paths from
.rtlocal.rc
, which is effectively read-only, to.rtorrent.rc
, which can modified by the user without having to rebuild the container.