-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
rutorrent: fix volume customization in installation procedure and package dependencies #5669
rutorrent: fix volume customization in installation procedure and package dependencies #5669
Conversation
I tried doing a clean install in DSM 6 and setting a watch directory but got an error: I don't know if this is a new error or something from before. Below are some of the logs: /var/log/packages/rutorrent.log
/var/log/synopkg.log
|
@mreid-tt it's actually something which dates back from the previous versions which had gone through the cracks. Will push a fix in this MR in the coming EDIT: Updated the ETA (sorry but I realized that I needed to reset my dev environment) |
Converting to draft until I confirm that I've fixed the watch directory issue reported above. |
Flagged as draft as I spotted another bug with the watch directory (not actually configured appropriately) |
Okay, it looks like we thought of the same thing... As an update the torrent in the watch folder eventually downloaded on its own so there was some delay but it should be good now. |
Regarding my other #5617 (comment), where we discussed:
What I was trying to share was the recommended configuration for the Web Service in the DSM 7 developer guide. In it the following common keys are mandatory: When I initially looked at your resource file I missed that the |
@smaarn, I can confirm that the last patch fixed the watch folder and torrent files added to it are automatically downloaded. |
Are there any plans to support nginx as a backend or Apache will remain as hard dependency for rutorrent installation? |
As has been stated before in this #5617 (comment), there are no explicit plans for this. As you have asked this before, I would suggest you open a new issue specifically requesting that the backend support nginx. That way it can be tracked and responded to formally. @smaarn, based on your previous comment there would likely have to be a hard switch from Apache to nginx as the package dependencies cannot allow for an either/or scenario. This document may assist with possible testing configurations: NGINX PHP FPM RTORRENT |
Description
This is fixing basically installation related concerns:
Should fix #5668
Checklist
all-supported
completed successfullyType of change