Split Autopirate into uber-recipe

manuscript/recipies/autopirate.md

@@ -145,6 +145,7 @@ sabnzbd_proxy:
 ````
 nzbget:
   image: linuxserver/nzbget
+  env_file : /var/data/config/autopirate/nzbget.env  
   volumes:
    - /var/data/autopirate/nzbget:/config
    - /var/data/media:/data

manuscript/recipies/autopirate/end.md

@@ -0,0 +1,16 @@
+hero: AutoPirate - A fully-featured recipe to automate finding, downloading, and organising your media 📺 🎥 🎵 📖
+
+
+### Launch Autopirate stack
+
+Launch the AutoPirate stack by running ```docker stack deploy autopirate -c <path -to-docker-compose.yml>```
+
+Confirm the container status by running "docker stack ps autopirate", and wait for all containers to enter the "Running" state.
+
+Log into each of your new tools at its respective HTTPS URL. You'll be prompted to authenticate against your OAuth provider, and upon success, redirected to the tool's UI.
+
+## 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?

manuscript/recipies/autopirate/headphones.md

@@ -0,0 +1,62 @@
+hero: AutoPirate - A fully-featured recipe to automate finding, downloading, and organising your media 📺 🎥 🎵 📖
+
+!!! warning
+    This is not a complete recipe - it's a component of the [autopirate](/recipies/autopirate/start/) "_uber-recipe_", but has been split into its own page to reduce complexity.
+
+# NAME
+
+Intro
+
+![Headphones Screenshot](../../images/headphones.png)
+
+Details
+
+## Inclusion into AutoPirate
+
+To include NZBGet in your [AutoPirate](/recipies/autopirate/start/) stack, 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``` 👍
+        
+````
+headphones:
+  image: linuxserver/headphones:latest
+  env_file : /var/data/config/autopirate/headphones.env
+  volumes:
+   - /var/data/autopirate/headphones:/config
+   - /var/data/media:/media
+  networks:
+  - traefik_public
+
+headphones_proxy:
+  image: zappi/oauth2_proxy
+  env_file : /var/data/config/autopirate/headphones.env
+  dns_search: myswarm.example.com  
+  networks:
+    - internal
+    - traefik_public
+  deploy:
+    labels:
+      - traefik.frontend.rule=Host:headphones.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://headphones:8181
+    -redirect-url=https://headphones.example.com
+    -http-address=http://0.0.0.0:4180
+    -email-domain=example.com
+    -provider=github
+    -authenticated-emails-file=/authenticated-emails.txt
+````
+
+!!! 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``` 👍
+
+## 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?

manuscript/recipies/autopirate/lazylibrarian.md

@@ -0,0 +1,62 @@
+!!! warning
+    This is not a complete recipe - it's a component of the [autopirate](/recipies/autopirate/start/) "_uber-recipe_", but has been split into its own page to reduce complexity.
+
+# NAME
+
+Intro
+
+![Lazy Librarian Screenshot](../../images/lazylibrarian.png)
+
+Details
+
+
+## Inclusion into AutoPirate
+
+To include NZBGet in your [AutoPirate](/recipies/autopirate/start/) stack, 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``` 👍
+
+````
+lazylibrarian:
+  image: linuxserver/lazylibrarian:latest
+  env_file : /var/data/config/autopirate/lazylibrarian.env
+  volumes:
+   - /var/data/autopirate/lazylibrarian:/config
+   - /var/data/media:/media
+  networks:
+  - traefik_public
+
+lazylibrarian_proxy:
+  image: zappi/oauth2_proxy
+  env_file : /var/data/config/autopirate/lazylibrarian.env
+  dns_search: myswarm.example.com  
+  networks:
+    - internal
+    - traefik_public
+  deploy:
+    labels:
+      - traefik.frontend.rule=Host:lazylibrarian.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://lazylibrarian:5299
+    -redirect-url=https://lazylibrarian.example.com
+    -http-address=http://0.0.0.0:4180
+    -email-domain=example.com
+    -provider=github
+    -authenticated-emails-file=/authenticated-emails.txt
+````
+
+!!! 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``` 👍
+
+
+## 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?

manuscript/recipies/autopirate/mylar.md

@@ -0,0 +1,60 @@
+!!! warning
+    This is not a complete recipe - it's a component of the [autopirate](/recipies/autopirate/start/) "_uber-recipe_", but has been split into its own page to reduce complexity.
+
+# NAME
+
+Intro
+
+![Mylar Screenshot](../../images/mylar.jpg)
+
+Details
+
+## Inclusion into AutoPirate
+
+To include NZBGet in your [AutoPirate](/recipies/autopirate/start/) stack, 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``` 👍
+
+````
+mylar:
+  image: linuxserver/mylar:latest
+  env_file : /var/data/config/autopirate/mylar.env
+  volumes:
+   - /var/data/autopirate/mylar:/config
+   - /var/data/media:/media
+  networks:
+  - traefik_public
+  -
+mylar_proxy:
+  image: zappi/oauth2_proxy
+  env_file : /var/data/config/autopirate/mylar.env
+  dns_search: myswarm.example.com  
+  networks:
+    - internal
+    - traefik_public
+  deploy:
+    labels:
+      - traefik.frontend.rule=Host:mylar.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://mylar:8090
+    -redirect-url=https://mylar.example.com
+    -http-address=http://0.0.0.0:4180
+    -email-domain=example.com
+    -provider=github
+    -authenticated-emails-file=/authenticated-emails.txt
+````
+
+!!! 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``` 👍
+
+## 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?

manuscript/recipies/autopirate/nzbget.md

@@ -0,0 +1,61 @@
+!!! warning
+    This is not a complete recipe - it's a component of the [AutoPirate](/recipies/autopirate/start/) "_uber-recipe_", but has been split into its own page to reduce complexity.
+
+# NZBGet
+
+## Introduction
+
+NZBGet performs the same function as [SABnzbd](/recipies/autopirate/sabnzbd.md) (_downloading content from Usenet servers_), but it's lightweight and fast(er), written in C++ (_as opposed to Python_).
+
+![NZBGet Screenshot](../../images/nzbget.jpg)
+
+## Inclusion into AutoPirate
+
+To include NZBGet in your [AutoPirate](/recipies/autopirate/start/) stack, 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``` 👍
+
+````
+nzbget:
+  image: linuxserver/nzbget
+  env_file : /var/data/config/autopirate/nzbget.env  
+  volumes:
+   - /var/data/autopirate/nzbget:/config
+   - /var/data/media:/data
+  networks:
+  - traefik_public
+
+nzbget_proxy:
+  image: zappi/oauth2_proxy
+  env_file : /var/data/config/autopirate/nzbget.env
+  dns_search: myswarm.example.com
+  networks:
+    - internal
+    - traefik_public
+  deploy:
+    labels:
+      - traefik.frontend.rule=Host:nzbget.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://nzbget:6789
+    -redirect-url=https://nzbget.example.com
+    -http-address=http://0.0.0.0:4180
+    -email-domain=example.com
+    -provider=github
+    -authenticated-emails-file=/authenticated-emails.txt
+````
+
+!!! note
+    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
+
+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?

manuscript/recipies/autopirate/nzbhydra.md

@@ -0,0 +1,58 @@
+!!! warning
+    This is not a complete recipe - it's a component of the [AutoPirate](/recipies/autopirate/start/) "_uber-recipe_", but has been split into its own page to reduce complexity.
+
+
+#### NZBHydra
+
+![NZBHydra Screenshot](../../images/nzbhydra.png)
+
+
+## Inclusion into AutoPirate
+
+To include NZBGet in your [AutoPirate](/recipies/autopirate/start/) stack, 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``` 👍
+
+````
+nzbhydra:
+  image: linuxserver/hydra:latest
+  env_file : /var/data/config/autopirate/nzbhydra.env
+  volumes:
+   - /var/data/autopirate/nzbhydra:/config
+  networks:
+  - traefik_public
+
+nzbhydra_proxy:
+  image: zappi/oauth2_proxy
+  env_file : /var/data/config/autopirate/nzbhydra.env
+  dns_search: myswarm.example.com  
+  networks:
+    - internal
+    - traefik_public
+  deploy:
+    labels:
+      - traefik.frontend.rule=Host:nzbhydra.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://nzbhydra:5075
+    -redirect-url=https://nzbhydra.example.com
+    -http-address=http://0.0.0.0:4180
+    -email-domain=example.com
+    -provider=github
+    -authenticated-emails-file=/authenticated-emails.txt
+````
+
+!!! 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``` 👍
+
+
+## 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?

manuscript/recipies/autopirate/ombi.md

@@ -0,0 +1,61 @@
+!!! warning
+    This is not a complete recipe - it's a component of the [AutoPirate](/recipies/autopirate/start/) "_uber-recipe_", but has been split into its own page to reduce complexity.
+
+# NAME
+
+Intro
+
+![Ombi Screenshot](../../images/ombi.png)
+
+Details
+
+## Ombi
+
+## Inclusion into AutoPirate
+
+To include NZBGet in your [AutoPirate](/recipies/autopirate/start/) stack, 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``` 👍
+
+````
+ombi:
+  image: linuxserver/ombi:latest
+  env_file : /var/data/config/autopirate/ombi.env
+  volumes:
+   - /var/data/autopirate/ombi:/config
+  networks:
+  - traefik_public
+
+ombi_proxy:
+  image: zappi/oauth2_proxy
+  env_file : /var/data/config/autopirate/ombi.env
+  dns_search: myswarm.example.com  
+  networks:
+    - internal
+    - traefik_public
+  deploy:
+    labels:
+      - traefik.frontend.rule=Host:ombi.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://ombi:3579
+    -redirect-url=https://ombi.example.com
+    -http-address=http://0.0.0.0:4180
+    -email-domain=example.com
+    -provider=github
+    -authenticated-emails-file=/authenticated-emails.txt
+````
+
+!!! 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``` 👍
+
+## 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?

manuscript/recipies/autopirate/plexpy.md

@@ -0,0 +1,67 @@
+!!! warning
+    This is not a complete recipe - it's a component of the [AutoPirate](/recipies/autopirate/start/) "_uber-recipe_", but has been split into its own page to reduce complexity.
+
+# NAME
+
+Intro
+
+![Plexpy Screenshot](../../images/plexpy.png)
+
+Details
+
+
+
+
+
+
+#### Plexpy
+
+## Inclusion into AutoPirate
+
+To include NZBGet in your [AutoPirate](/recipies/autopirate/start/) stack, 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``` 👍
+
+````
+plexpy:
+  image: linuxserver/plexpy:latest
+  env_file : /var/data/config/autopirate/plexpy.env
+  volumes:
+   - /var/data/autopirate/plexpy:/config
+  networks:
+  - traefik_public
+
+plexpy_proxy:
+  image: zappi/oauth2_proxy
+  env_file : /var/data/config/autopirate/plexpy.env
+  dns_search: myswarm.example.com  
+  networks:
+    - internal
+    - traefik_public
+  deploy:
+    labels:
+      - traefik.frontend.rule=Host:plexpy.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://plexpy:8181
+    -redirect-url=https://plexpy.example.com
+    -http-address=http://0.0.0.0:4180
+    -email-domain=example.com
+    -provider=github
+    -authenticated-emails-file=/authenticated-emails.txt
+````
+
+!!! 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``` 👍
+
+
+## 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?

manuscript/recipies/autopirate/radarr.md

@@ -0,0 +1,60 @@
+!!! warning
+    This is not a complete recipe - it's a component of the [AutoPirate](/recipies/autopirate/start/) "_uber-recipe_", but has been split into its own page to reduce complexity.
+
+# Radarr
+
+Intro
+
+![Radarr Screenshot](../../images/radarr.png)
+
+Details
+
+## Inclusion into AutoPirate
+
+To include NZBGet in your [AutoPirate](/recipies/autopirate/start/) stack, 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``` 👍
+
+````
+radarr:
+  image: linuxserver/radarr:latest
+  env_file : /var/data/config/autopirate/radarr.env
+  volumes:
+   - /var/data/autopirate/radarr:/config
+   - /var/data/media:/media
+  networks:
+  - traefik_public
+
+radarr_proxy:
+  image: zappi/oauth2_proxy
+  env_file : /var/data/config/autopirate/radarr.env
+  dns_search: myswarm.example.com  
+  networks:
+    - internal
+    - traefik_public
+  deploy:
+    labels:
+      - traefik.frontend.rule=Host:radarr.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://radarr:7878
+    -redirect-url=https://radarr.example.com
+    -http-address=http://0.0.0.0:4180
+    -email-domain=example.com
+    -provider=github
+    -authenticated-emails-file=/authenticated-emails.txt
+````
+
+!!! 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``` 👍
+
+## 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?

manuscript/recipies/autopirate/rtorrent.md

@@ -0,0 +1,62 @@
+!!! warning
+    This is not a complete recipe - it's a component of the [AutoPirate](/recipies/autopirate/start/) "_uber-recipe_", but has been split into its own page to reduce complexity.
+
+# RTorrent / ruTorrent
+
+![Rtorrent Screenshot](../../images/rtorrent.png)
+
+When using a torrent client from behind NAT (_which swarm, by nature, is_), you typically need to set a static port for inbound torrent communications. In the example below, I've set the port to 36258. You'll need to configure /var/data/autopirate/rtorrent/rtorrent/rtorrent.rc with the equivalent port.
+
+## Inclusion into AutoPirate
+
+To include NZBGet in your [AutoPirate](/recipies/autopirate/start/) stack, 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``` 👍
+
+
+```
+rtorrent:
+  image: linuxserver/rutorrent
+  env_file : /var/data/config/autopirate/rtorrent.env
+  ports:
+   - 36258:36258
+  volumes:
+   - /var/data/media/:/media
+   - /var/data/autopirate/rtorrent:/config
+  networks:
+  - internal
+
+rtorrent_proxy:
+  image: skippy/oauth2_proxy
+  env_file : /var/data/config/autopirate/rtorrent.env
+  dns_search: myswarm.example.com
+  networks:
+    - internal
+    - traefik_public
+  deploy:
+    labels:
+      - traefik.frontend.rule=Host:rtorrent.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://rtorrent:80
+    -redirect-url=https://rtorrent.example.com
+    -http-address=http://0.0.0.0:4180
+    -email-domain=example.com
+    -provider=github
+    -authenticated-emails-file=/authenticated-emails.txt
+```
+
+!!! 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``` 👍
+
+
+## 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?

manuscript/recipies/autopirate/sabnzbd.md

@@ -0,0 +1,54 @@
+!!! warning
+    This is not a complete recipe - it's a component of the [AutoPirate](/recipies/autopirate/start/) "_uber-recipe_", but has been split into its own page to reduce complexity.
+
+# SABnzbd
+
+![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:
+
+!!! 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``` 👍
+
+````
+sabnzbd:
+  image: linuxserver/sabnzbd:latest
+  volumes:
+   - /var/data/autopirate/sabnzbd:/config
+   - /var/data/media:/media
+  networks:
+  - traefik_public
+
+sabnzbd_proxy:
+  image: zappi/oauth2_proxy
+  env_file : /var/data/config/autopirate/sabnzbd.env
+  dns_search: myswarm.example.com
+  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
+````
+
+
+
+## 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?

manuscript/recipies/autopirate/sonarr.md

@@ -0,0 +1,60 @@
+!!! warning
+    This is not a complete recipe - it's a component of the [AutoPirate](/recipies/autopirate/start/) "_uber-recipe_", but has been split into its own page to reduce complexity.
+
+
+# Sonarr
+
+![Sonarr Screenshot](../../images/sonarr.png)
+
+
+## Inclusion into AutoPirate
+
+To include NZBGet in your [AutoPirate](/recipies/autopirate/start/) stack, 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``` 👍
+
+````
+sonarr:
+  image: linuxserver/sonarr:latest
+  env_file : /var/data/config/autopirate/sonarr.env
+  volumes:
+   - /var/data/autopirate/sonarr:/config
+   - /var/data/media:/media
+  networks:
+  - traefik_public
+
+sonarr_proxy:
+  image: zappi/oauth2_proxy
+  env_file : /var/data/config/autopirate/sonarr.env
+  dns_search: myswarm.example.com  
+  networks:
+    - internal
+    - traefik_public
+  deploy:
+    labels:
+      - traefik.frontend.rule=Host:sonarr.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://sonarr:8989
+    -redirect-url=https://sonarr.example.com
+    -http-address=http://0.0.0.0:4180
+    -email-domain=example.com
+    -provider=github
+    -authenticated-emails-file=/authenticated-emails.txt
+````
+
+!!! 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``` 👍
+
+
+
+## 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?

mkdocs.yml

@@ -40,7 +40,18 @@ pages:
       - Kanboard: recipies/kanboard.md
       - Miniflux: recipies/miniflux.md
       - Gollum: recipies/gollum.md
-      - AutoPirate: recipies/autopirate.md
+      - Auto Pirate:
+        - Start: recipies/autopirate.md
+        - SABnzbd: recipies/autopirate/sabnzbd.md
+        - NZBGet: recipies/autopirate/nzbget.md
+        - Rtorrent: recipies/autopirate/rtorrent.md
+        - Sonarr: recipies/autopirate/sonarr.md
+        - Radarr: recipies/autopirate/radarr.md
+        - Mylar: recipies/autopirate/mylar.md
+        - Lazy Librarian: recipies/autopirate/lazylibrarian.md
+        - Ombi: recipies/autopirate/ombi.md
+        - Plexpy: recipies/autopirate/plexpy.md
+        - End: recipies/autopirate/end.md
       - NextCloud: recipies/nextcloud.md
       - Plex: recipies/plex.md
       - Emby: recipies/emby.md
@@ -59,7 +70,7 @@ pages:
       - Networks: reference/networks.md
       - git-docker : reference/git-docker.md
       - OpenVPN : reference/openvpn.md
-      - Troubleshooting: reference/troubleshooting.md      
+      - Troubleshooting: reference/troubleshooting.md
     - Support: support.md
 
 theme: