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 b396014f8d 9 years ago
cherrypy CherrpPy patch: prevent crash on some special URI-s. 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 Replace current icon files with smaller ones (thanks, inpheaux). 13 years ago
interfaces Add trailing "/" to href's 9 years ago
licenses Remove Json.py license 10 years ago
linux add (example) systemd unit file 11 years ago
osx Update unrar for OSX to 5.30 10 years ago
po Update translations 9 years ago
sabnzbd Fix IP test at startup. 9 years ago
scripts Some pep8 cleanup (whitespace/docstring only), focus on root dir along with scripts/tools/util. 10 years ago
solaris Adds solaris manifest 11 years ago
tools Some pep8 cleanup (whitespace/docstring only), focus on root dir along with scripts/tools/util. 10 years ago
util Some pep8 cleanup (whitespace/docstring only), focus on root dir along with scripts/tools/util. 10 years ago
win Update unrar for Windows and OSX to 5.30 10 years ago
.gitignore Support testing email based on values in UI instead of stored config. 11 years ago
ABOUT.txt Update text files for 1.0.xRC1 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 text files for 1.0.xRC1 9 years ago
ISSUES.txt Fix links in text files to pooit to 1.0.0 entries in the Wiki. 9 years ago
LICENSE.txt Update to 2016. 9 years ago
PKG-INFO Update text files for 1.0.0RC2 9 years ago
README.md Update README 9 years ago
README.mkd Update text files for 1.0.0RC2 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 Fix IP test at startup. 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

We're going to be attempting to follow the gitflow model, so you can consider "master" to be whatever our present stable release build is (presently 0.6.x) and "develop" to be whatever our next build will be (presently 0.7.x). Once we transition from unstable to stable dev builds we'll create release branches, and encourage you to follow along and help us test.