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 3dea948ecc Update text files for 0.6.9 RC1. 14 years ago
cherrypy Add CherryPy module as complete source tree. 14 years ago
email Capitalize keywords in email templates according to convention. 15 years ago
interfaces Reverted hoverIntent version back to r5. It was breaking the menu. 14 years ago
licenses Update Curl license text. 14 years ago
osx Update UnRAR to release 4.01 14 years ago
po Update translations. 14 years ago
sabnzbd Check email parameters also when only email_rss option is enabled. 14 years ago
tools Output po/nsis/SABnsis.pot in Unix format too. 14 years ago
util Win32: Fix registration of SABnzbd url in the user registry. This made the NZB association go wrong. 14 years ago
win Update UnRAR to release 4.01 14 years ago
.gitignore Make package.py work in a git environment. 14 years ago
ABOUT.txt Update text files for 0.6.9 RC1. 14 years ago
CHANGELOG.txt Update text files for 0.6.9 RC1. 14 years ago
COPYRIGHT.txt Merge LICENSE.txt and COPYRIGHT.txt into just one file: COPYRIGHT.txt. 15 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 0.6.9 RC1. 14 years ago
ISSUES.txt Add INI-only option "api_warnings" to enable/disable warnings about unauthenticated access to the API. 15 years ago
LICENSE.txt Restore LICENSE.txt. 15 years ago
NSIS_Installer.nsi The NSIS uninstaller must remove Romanian email templates too. 14 years ago
PKG-INFO Update text files for 0.6.9 RC1. 14 years ago
README.md Kill .bzr stuff, add .gitignore & a pretty README.md for GitHub. 14 years ago
README.rtf Update text files for 0.6.9 RC1. 14 years ago
README.txt Update text files for 0.6.9 RC1. 14 years ago
SABHelper.py Update copyrights to 2011. 15 years ago
SABnzbd.py Setting of WIN64 flag was done only after selecting unrar/par2 variants. 14 years ago
Sample-PostProc.cmd Eliminate superfluous 'main' folder 15 years ago
Sample-PostProc.sh Eliminate superfluous 'main' folder 15 years ago
nzb.ico Eliminate superfluous 'main' folder 15 years ago
package.py Use different background images for Lion and (Snow)Leopard DMG files. 14 years ago
sabnzbd.ico Eliminate superfluous 'main' folder 15 years ago
setup.py Set x-bit for setup.py and package.py 15 years ago

README.md

SABnzbd - The automated Usenet download tool

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.5-2.7, preferably 2.6 or 2.7.)
  • python-cheetah
  • python-configobj
  • python-feedparser
  • python-dbus
  • python-openssl
  • python-support
  • python-yenc
  • par2 (Multi-threaded par2 can be downloaded from ChuChuSoft )
  • unrar (Make sure you get the "official" non-free version of unrar)
  • unzip

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 -d -f /path/to/sabnzbd.ini

If you want multi-language support, run:

python tools/make_mo.py

Our many other commandline 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.