mirror of
https://github.com/funkypenguin/geek-cookbook/
synced 2026-10-30 20:48:21 +00:00
David Young
745dc26946
* Test updating CTA, using insiders version of mkdocs-material * Dark mode, baby! Signed-off-by: David Young <davidy@funkypenguin.co.nz> * What will netlify do if I remove requirements.txt? Signed-off-by: David Young <davidy@funkypenguin.co.nz> * What will netlify do if I remove requirements.txt? Signed-off-by: David Young <davidy@funkypenguin.co.nz> * Only build the insiders version Signed-off-by: David Young <davidy@funkypenguin.co.nz> * Remove some broken links Signed-off-by: David Young <davidy@funkypenguin.co.nz> * Fix dead link Signed-off-by: David Young <davidy@funkypenguin.co.nz> * Remove twitter embed Signed-off-by: David Young <davidy@funkypenguin.co.nz> * Fix dead links Signed-off-by: David Young <davidy@funkypenguin.co.nz> * Mooar dead links Signed-off-by: David Young <davidy@funkypenguin.co.nz> * Final dead link Signed-off-by: David Young <davidy@funkypenguin.co.nz>
82 lines
3.8 KiB
Markdown
82 lines
3.8 KiB
Markdown
!!! warning
|
|
This is not a complete recipe - it's a component of the [AutoPirate](/recipes/autopirate/) "_uber-recipe_", but has been split into its own page to reduce complexity.
|
|
|
|
# SABnzbd
|
|
|
|
## Introduction
|
|
|
|
SABnzbd is the workhorse of the stack. It takes .nzb files as input (_manually or from other [autopirate](/recipes/autopirate/) stack tools_), then connects to your chosen Usenet provider, downloads all the individual binaries referenced by the .nzb, and then tests/repairs/combines/uncompresses them all into the final result - media files.
|
|
|
|
|
|
|
|
## Inclusion into AutoPirate
|
|
|
|
To include SABnzbd in your [AutoPirate](/recipes/autopirate/) stack
|
|
(_The only reason you **wouldn't** use SABnzbd, would be if you were using [NZBGet](/recipes/autopirate/nzbget.md) instead_), include the following in your autopirate.yml stack definition file:
|
|
|
|
--8<-- "premix-cta.md"
|
|
|
|
````
|
|
sabnzbd:
|
|
image: linuxserver/sabnzbd:latest
|
|
env_file : /var/data/config/autopirate/sabnzbd.env
|
|
volumes:
|
|
- /var/data/autopirate/sabnzbd:/config
|
|
- /var/data/media:/media
|
|
networks:
|
|
- internal
|
|
|
|
sabnzbd_proxy:
|
|
image: a5huynh/oauth2_proxy
|
|
env_file : /var/data/config/autopirate/sabnzbd.env
|
|
networks:
|
|
- internal
|
|
- traefik_public
|
|
deploy:
|
|
labels:
|
|
- traefik.frontend.rule=Host:sabnzbd.example.com
|
|
- traefik.docker.network=traefik_public
|
|
- traefik.port=4180
|
|
volumes:
|
|
- /var/data/config/autopirate/authenticated-emails.txt:/authenticated-emails.txt
|
|
command: |
|
|
-cookie-secure=false
|
|
-upstream=http://sabnzbd:8080
|
|
-redirect-url=https://sabnzbd.example.com
|
|
-http-address=http://0.0.0.0:4180
|
|
-email-domain=example.com
|
|
-provider=github
|
|
-authenticated-emails-file=/authenticated-emails.txt
|
|
````
|
|
|
|
!!! warning "Important Note re hostname validation"
|
|
|
|
(**Updated 10 June 2018**) : In SABnzbd [2.3.3](https://sabnzbd.org/wiki/extra/hostname-check.html), hostname verification was added as a mandatory check. SABnzbd will refuse inbound connections which weren't addressed to its own (_initially, autodetected_) hostname. This presents a problem within Docker Swarm, where container hostnames are random and disposable.
|
|
|
|
You'll need to edit sabnzbd.ini (_only created after your first launch_), and **replace** the value in ```host_whitelist``` configuration (_it's comma-separated_) with the name of your service within the swarm definition, as well as your FQDN as accessed via traefik.
|
|
|
|
For example, mine simply reads ```host_whitelist = sabnzbd.funkypenguin.co.nz, sabnzbd```
|
|
|
|
## Assemble more tools..
|
|
|
|
Continue through the list of tools below, adding whichever tools your want to use, and finishing with the **[end](/recipes/autopirate/end/)** section:
|
|
|
|
* SABnzbd (this page)
|
|
* [NZBGet](/recipes/autopirate/nzbget.md)
|
|
* [RTorrent](/recipes/autopirate/rtorrent/)
|
|
* [Sonarr](/recipes/autopirate/sonarr/)
|
|
* [Radarr](/recipes/autopirate/radarr/)
|
|
* [Mylar](/recipes/autopirate/mylar/)
|
|
* [Lazy Librarian](/recipes/autopirate/lazylibrarian/)
|
|
* [Headphones](/recipes/autopirate/headphones/)
|
|
* [Lidarr](/recipes/autopirate/lidarr/)
|
|
* [NZBHydra](/recipes/autopirate/nzbhydra/)
|
|
* [NZBHydra2](/recipes/autopirate/nzbhydra2/)
|
|
* [Ombi](/recipes/autopirate/ombi/)
|
|
* [Jackett](/recipes/autopirate/jackett/)
|
|
* [Heimdall](/recipes/autopirate/heimdall/)
|
|
* [End](/recipes/autopirate/end/) (launch the stack)
|
|
|
|
[^1]: In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.
|
|
|
|
--8<-- "recipe-footer.md" |