Improved SAB/NZBGet sub-recipies

2026-11-06 15:28:18 +00:00 · 2018-01-02 16:38:43 +13:00
1 parent 36debb39ad
commit 9e7e6cbcff
@@ -1,5 +1,5 @@
-hero: AutoPirate - A fully-featured recipe to automate finding, downloading, and organising your media 📺 🎥 🎵 📖
-
+!!! warning
+    This is not a complete recipe - it's the conclusion to the [AutoPirate](/recipies/autopirate/start/) "_uber-recipe_", but has been split into its own page to reduce complexity.

 ### Launch Autopirate stack

@@ -11,7 +11,8 @@ NZBGet performs the same function as [SABnzbd](/recipies/autopirate/sabnzbd.md)

 ## Inclusion into AutoPirate

-To include NZBGet in your [AutoPirate](/recipies/autopirate/start/) stack, include the following in your autopirate.yml stack definition file:
+To include NZBGet in your [AutoPirate](/recipies/autopirate/start/) stack
+(_The only reason you **wouldn't** use NZBGet, would be if you were using [SABnzbd](/recipies/autopirate/sabnzbd/) instead_), include the following in your autopirate.yml stack definition file:

 !!! tip
        I share (_with my [patreon patrons](https://www.patreon.com/funkypenguin)_) a private "_premix_" git repository, which includes necessary docker-compose and env files for all published recipes. This means that patrons can launch any recipe with just a ```git pull``` and a ```docker stack deploy``` 👍
@@ -54,8 +55,29 @@ nzbget_proxy:
    NZBGet uses a 401 header to prompt for authentication. When you use OAuth2_proxy, this seems to break. Since we trust OAuth to authenticate us, we can just disable NZGet's own authentication, by changing ControlPassword to null in nzbget.conf (i.e. ```ControlPassword=```)


-## Chef's Notes
+## Assemble more tools..
+
+Continue through the list of tools below, adding whichever tools your want to use, and finishing with the **[end](/recipies/autopirate/end/)** section:
+
+* [SABnzbd](/recipies/autopirate/sabnzbd.md)
+* NZBGet (this page)
+* [RTorrent](/recipies/autopirate/rtorrent/)
+* [Sonarr](/recipies/autopirate/sonarr/)
+* [Radarr](/recipies/autopirate/radarr/)
+* [Mylar](/recipies/autopirate/mylar/)
+* [Lazy Librarian](/recipies/autopirate/lazylibrarian/)
+* [Headphones](/recipies/autopirate/headphones/)
+* [NZBHydra](/recipies/autopirate/nzbhydra/)
+* [Ombi](/recipies/autopirate/ombi/)
+* [End](/recipies/autopirate/end/) (launch the stack)
+
+
+## Chef's Notes 📓

 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.

-## Your comments?
+### Tip your waiter (donate) 👏
+
+Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏
+
+### Your comments? 💬
@@ -3,11 +3,16 @@

 # SABnzbd

+## Introduction
+
+SABnzbd is the workhorse of the stack. It takes .nzb files as input (_manually or from other [autopirate](/recipies/autopirate/start/) 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.
+
 ![SABNZBD Screenshot](../../images/sabnzbd.png)

 ## Inclusion into AutoPirate

-To include NZBGet in your [AutoPirate](/recipies/autopirate/start/) stack, include the following in your autopirate.yml stack definition file:
+To include SABNZBD in your [AutoPirate](/recipies/autopirate/start/) stack
+(_The only reason you **wouldn't** use SABnzbd, would be if you were using [NZBGet](/recipies/autopirate/nzbget.md) instead_), include the following in your autopirate.yml stack definition file:

 !!! tip
        I share (_with my [patreon patrons](https://www.patreon.com/funkypenguin)_) a private "_premix_" git repository, which includes necessary docker-compose and env files for all published recipes. This means that patrons can launch any recipe with just a ```git pull``` and a ```docker stack deploy``` 👍
@@ -15,6 +20,7 @@ To include NZBGet in your [AutoPirate](/recipies/autopirate/start/) stack, inclu
 ````
 sabnzbd:
  image: linuxserver/sabnzbd:latest
+  env_file : /var/data/config/autopirate/sabnzbd.env  
  volumes:
   - /var/data/autopirate/sabnzbd:/config
   - /var/data/media:/media
@@ -45,10 +51,29 @@ sabnzbd_proxy:
    -authenticated-emails-file=/authenticated-emails.txt
 ````

+## Assemble more tools..
+
+Continue through the list of tools below, adding whichever tools your want to use, and finishing with the **[end](/recipies/autopirate/end/)** section:
+
+* SABnzbd (this page)
+* [NZBGet](/recipies/autopirate/nzbget.md)
+* [RTorrent](/recipies/autopirate/rtorrent/)
+* [Sonarr](/recipies/autopirate/sonarr/)
+* [Radarr](/recipies/autopirate/radarr/)
+* [Mylar](/recipies/autopirate/mylar/)
+* [Lazy Librarian](/recipies/autopirate/lazylibrarian/)
+* [Headphones](/recipies/autopirate/headphones/)
+* [NZBHydra](/recipies/autopirate/nzbhydra/)
+* [Ombi](/recipies/autopirate/ombi/)
+* [End](/recipies/autopirate/end/) (launch the stack)


-## Chef's Notes
+## Chef's Notes 📓

 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.

-## Your comments?
+### Tip your waiter (donate) 👏
+
+Did you receive excellent service? Want to make your waiter happy? (_..and support development of current and future recipes!_) See the [support](/support/) page for (_free or paid)_ ways to say thank you! 👏
+
+### Your comments? 💬