Support Forum

I just pushed a new version. It contains some bugfixes and minor cosmetic changes, also there are two new options: authRequired and downloadAuthRequired. When the first one is set you need to login to access sabRE. When the second one is set, downloads from sabRE (.tar archives) are allowed without ...

Some minutes ago a new version was published. The postprocessing scripts can now convert .flac files to .mp3 files when the needed tools are installed and the user desired the conversion. Also a new setting to hide downloads after a configurable number of days was introduced. Some other minor stuff ...

I just pushed a new version. It now listens on IPv6, additionally there is a new option to rename windows executables that can be switched on/off in "sabre_settings.py". I hope everything went right - this was my first commit using Git on Linux from the shell... Don't forget to run "n...

Very nice. I will push this to GitHub soon.
BTW, if you update your copy after my push, you will have to do "npm install" before starting sabRE. I hope everything works afterwards because I changed some things, if not I am here for new bug reports ...

Replace the line "app.listen settings.port, () =>" in app.coffee with "app.listen settings.port, '::', () =>". Then sabRE should listen on IPv6, too.

Hi sander, sorry for my late reply! The remoteauth part is - despite your explanation - still dark matter to me. I will explain it in detail now. I hope it is understandable. When a user logs in, sabRE checks the users.json file if the user is allowed to login. If the user is not defined in users.js...

Nice to hear, thank you!

Nice to hear that most stuff works. :) Download results: Download works, the result is in the sabRE's GUI, but user1's download just arrives in :~/Downloads/complete/. That means (AFAIK) there is no way to share it to a specific user. I would have expected a directory per user defines in sabRE's con...

I just pushed a new version, I think everything you suggested is included. By setting the value of "noPostProcess" you can control if sabRE will create tar files or use categories for each user to download files (so you can setup shares for each user pointing to that directory).

Ah, do you mean this: the separate files of a download are packed into one tar file, which makes remote downloading via een webinterface easier? Exactly. It does not run on a local LAN for me and is only reachable using HTTP, so I needed an easy way to let users download files. I implemented your u...

To get it the way you suggest, one has to use categories (you suggested that on the first page of this thread I think) or one would have to modify the postprocessing script so that it would create the users dir, but the first option makes more sense I think. Then sabRE needs to set the category when...

Regarding the issue with the my_home I think it can be solved without doing the API call, which makes it easier for me (looked at SABnzbd.py file). You aren't running SABnzbd in daemon mode I think, so it uses your home directory. I run it in daemon mode, so it uses it's installation path and does n...

Very nice, I think using this information I can fix it. If I have to go the way with the API it will be some more work, because I would first have to be sure the user has entered the right IP/Port/API-Key, and then I would be able to get the complete dir. So it would be a setup with two "stages...

It makes sense what you say, and I would have thought that it works this way. But why does my SABnzbd not behave this way? In Settings->Folders, SABnzbd states on top of the page: "Default Base Folder: /home/user/.sabnzbd" and I read the only way to change this folder is by running SABnzbd...

Hmm, how does your SABnzbd interpret the relative path? If you use "Downloads/complete", where get your files saved? On my setup, they would get saved to "/home/user/.sabnzbd/Downloads/complete". Also the directory has to exist when importing settings.