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: https://sabnzbd.org.
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, then you likely already have all the needed dependencies. If not, here's what you're looking for:
python(only 2.7.x and higher, but not 3.x.x)
par2(Multi-threaded par2 installation guide can be found here)
unrar(Make sure you get the "official" non-free version of unrar)
sabyenc(installation guide can be found here)
python-cryptography(enables certificate generation and detection of encrypted RAR-files during download)
python-dbus(enable option to Shutdown/Restart/Standby PC on queue finish)
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 -OO SABnzbd.py
Or, if you want to run in the background:
python -OO SABnzbd.py -d -f /path/to/sabnzbd.ini
If you want multi-language support, run:
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:
mastercontains only stable releases (which have been merged to
master) and is intended for end-users.
developis the target for integration and is not intended for end-users.
1.1.xis a release and maintenance branch for 1.1.x (1.1.0 -> 1.1.1 -> 1.1.2) and is not intended for end-users.
feature/my_featureis a temporary feature branch based on
bugfix/my_bugfixis an optional temporary branch for bugfix(es) based on
- Merging of a stable release into
masterwill be simple: the release branch is always right.
masteris not merged back to
developis not re-based on
- Release branches branch from
- Bugfixes created specifically for a release branch are done there (because they are specific, they're not cherry-picked to
- Bugfixes done on
developmay be cherry-picked to a release branch.
- We will not release a 1.0.2 if a 1.1.0 has already been released.