You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
shypike 9e46f8adbc A lot of nonfunctional changes from PyLint advice. 9 years ago
cherrypy Patch CherryPy 6.0.2 : Implement 301 redirection for http-->https 9 years ago
email Email notification for failed URL fetches. 13 years ago
gntp Remove warning about Growl when user has disabled message class in Growl itself. 13 years ago
icons Create new ICO files 9 years ago
interfaces Catch all needed update-times 9 years ago
licenses Add the module "six". 9 years ago
linux Update Wiki-link 9 years ago
osx Update unrar for OSX to 5.30 10 years ago
po Update translatable texts. 9 years ago
sabnzbd A lot of nonfunctional changes from PyLint advice. 9 years ago
scripts Some pep8 cleanup (whitespace/docstring only), focus on root dir along with scripts/tools/util. 10 years ago
six Add the module "six". 9 years ago
solaris Adds solaris manifest 11 years ago
tools A lot of nonfunctional changes from PyLint advice. 9 years ago
util Some pep8 cleanup (whitespace/docstring only), focus on root dir along with scripts/tools/util. 10 years ago
win Update 7zip for Windows to latest release and enforce 7zip format when unpacking. 9 years ago
.gitignore Ignore .pyd too 9 years ago
ABOUT.txt Remove code for v0.5.x 9 years ago
COPYRIGHT.txt Update to 2016. 9 years ago
Dockerfile Add Dockerfile 11 years ago
GPL2.txt Eliminate superfluous 'main' folder 15 years ago
GPL3.txt Eliminate superfluous 'main' folder 15 years ago
INSTALL.txt Update Wiki-link 9 years ago
ISSUES.txt Update Wiki-link 9 years ago
LICENSE.txt Update to 2016. 9 years ago
PKG-INFO Update text file for 1.1.0RC2 9 years ago
README.md Update Wiki-link 9 years ago
README.mkd Add credit for XSS vulnerability discovery 9 years ago
SABHelper.py moved regex define before use (save memory when code branch isnt ran), calculate expire time once (save cpu cycles), reserved word (only some) & undefined & unused variables, depreciated `has_key`, more spelling and docstring cleanup 10 years ago
SABnzbd.py Encoding was logged twice (line 1250) 9 years ago
portable.cmd Make sure that the invoking window disappears 9 years ago

README.md

SABnzbd - The automated Usenet download tool

This Unicode release is not compatible with 0.7.x queues!

There is also an issue with upgrading of the "sabnzbd.ini" file. Make sure that you have a backup!

Saved queues may not be compatible after updates.


SABnzbd is an Open Source Binary Newsreader written in Python.

It's totally free, incredibly easy to use, and works practically everywhere.

SABnzbd makes Usenet as simple and streamlined as possible by automating everything we can. All you have to do is add an .nzb. SABnzbd takes over from there, where it will be automatically downloaded, verified, repaired, extracted and filed away with zero human interaction.

If you want to know more you can head over to our website: http://sabnzbd.org.

Resolving Dependencies

SABnzbd has a good deal of dependencies you'll need before you can get running. If you've previously run SABnzbd from one of the various Linux packages floating around (Ubuntu, Debian, Fedora, etc), then you likely already have all the needed dependencies. If not, here's what you're looking for:

  • python (We support Python 2.6 and 2.7)
  • python-cheetah
  • python-dbus
  • python-openssl
  • python-support
  • python-yenc
  • par2 (Multi-threaded par2 installation guide can be found here )
  • unrar (Make sure you get the "official" non-free version of unrar)
  • unzip
  • 7zip

Your package manager should supply these. If not, we've got links in our more in-depth installation guide.

Running SABnzbd from source

Once you've sorted out all the dependencies, simply run:

python SABnzbd.py

Or, if you want to run in the background:

python SABnzbd.py -d -f /path/to/sabnzbd.ini

If you want multi-language support, run:

python tools/make_mo.py

Our many other command line options are explained in depth here.

About Our Repo

The workflow we use, is a simplified form of "GitFlow". Basically:

  • "master" contains only stable releases (which have been merged to "master")
  • "develop" is the target for integration
  • "1.0.x" is a release and maintenance branch for 1.0.x: 1.0.0 -> 1.0.1 -> 1.0.2
  • "1.1.x" is a release and maintenance branch for 1.1.x: 1.1.0 -> 1.1.1 -> 1.1.2
  • "feature/my_feature" is a temporary feature branch
  • "hotfix/my_hotfix is an optional temporary branch for bugfix(es)

Condtions:

  • Merging of a stable release into "master" will be simple: the release branch is always right.
  • "master" is not merged back to "develop"
  • "develop" is not re-based on "master".
  • Release branches branch from "develop" only.
  • Bugfixes created specifically for a release branch are done there (because they are specific, they're not cherry-picked to "develop").
  • Bugfixes done on "develop" may be cherry-picked to a release branch.
  • We will not release a 1.0.2 if a 1.1.0 has already been released.