SABnzbd - Binary Newsgroup Reader
-
SABnzbd is a binary newsgroup reader. See https://sabnzbd.org/. Seems to be actively developed:
It is somewhat similar in functionality to NZBGet which was requested earlier. I was able to get this to run as an app on my cloudron and the repo for that package is here. It will need some polish and review though if it is to be used more generally. I can help with that if there is broader interest.
-
SABnzbd is a binary newsgroup reader. See https://sabnzbd.org/. Seems to be actively developed:
It is somewhat similar in functionality to NZBGet which was requested earlier. I was able to get this to run as an app on my cloudron and the repo for that package is here. It will need some polish and review though if it is to be used more generally. I can help with that if there is broader interest.
-
@esawtooth Ah thanks! I didn't realize this is a web application. Do you have any screenshot? Looks actively developed as you mentioned.
-
I had a question regarding the implementation of this app. I have currently put this behind the proxyAuth add-on but that prevents the app's APIs from being called by external applications, even if they use the API key. An alternative would be to use the app's inbuilt authentication which does not support LDAP and is limited to a single username/password combination. I have seen a similar issue with the transmission app as well, where the transmission's rpc api cannot be called by, say, the couchpotato app, due to the app being behind proxyApp.
What is the recommendation in such cases? Do we want to retain proxyAuth for a more secure and better integrated auth setup, or let users configure security using the in-app options available and allow them to retain access to the app's APIs.
Currently, I have put this behind proxyAuth, going by what was implemented for transmission, but more feedback might help make a better choice.
-
I had a question regarding the implementation of this app. I have currently put this behind the proxyAuth add-on but that prevents the app's APIs from being called by external applications, even if they use the API key. An alternative would be to use the app's inbuilt authentication which does not support LDAP and is limited to a single username/password combination. I have seen a similar issue with the transmission app as well, where the transmission's rpc api cannot be called by, say, the couchpotato app, due to the app being behind proxyApp.
What is the recommendation in such cases? Do we want to retain proxyAuth for a more secure and better integrated auth setup, or let users configure security using the in-app options available and allow them to retain access to the app's APIs.
Currently, I have put this behind proxyAuth, going by what was implemented for transmission, but more feedback might help make a better choice.
-
@esawtooth This has been an issue for other apps as well, so there's a
gitignore-style include-exclude sort of rule logic forproxyAuthcoming soon if not done already. cc @girish for the latest status on that@jimcavoli @esawtooth I have this for the coming release - https://git.cloudron.io/cloudron/box/-/issues/762
-
@jimcavoli @esawtooth I have this for the coming release - https://git.cloudron.io/cloudron/box/-/issues/762
-
@girish I see that the WIP tag has been removed from this. Let me know if any blocker fixes are needed on this, or if there are any review comments on the package.
@esawtooth Ah sorry, I thought this still needed some fixing with regards to proxyAuth. You mentioned that the app's API cannot be called from external apps. You can now put that as "!/api/path" - https://docs.cloudron.io/custom-apps/addons/#proxyauth
-
@esawtooth Ah sorry, I thought this still needed some fixing with regards to proxyAuth. You mentioned that the app's API cannot be called from external apps. You can now put that as "!/api/path" - https://docs.cloudron.io/custom-apps/addons/#proxyauth
-
@girish Sure, I'll make that change this weekend and update the app. I was under the impression that this would require a cloudron update
