Separated autopirate components

manuscript/recipies/autopirate/headphones.md

@@ -3,21 +3,16 @@ hero: AutoPirate - A fully-featured recipe to automate finding, downloading, and
 !!! 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
+# Headphones
 
-Intro
+[Headphones](https://github.com/rembo10/headphones) is an automated music downloader for NZB and Torrent, written in Python. It supports SABnzbd, NZBget, Transmission, µTorrent, Deluge and Blackhole.
 
 ![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:
+To include Headphones 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
@@ -26,7 +21,7 @@ headphones:
    - /var/data/autopirate/headphones:/config
    - /var/data/media:/media
   networks:
-  - traefik_public
+  - internal
 
 headphones_proxy:
   image: zappi/oauth2_proxy
@@ -53,10 +48,32 @@ headphones_proxy:
 ````
 
 !!! 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``` 👍
+    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
+## 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](/recipies/autopirate/nzbget.md)
+* [RTorrent](/recipies/autopirate/rtorrent/)
+* [Sonarr](/recipies/autopirate/sonarr/)
+* [Radarr](/recipies/autopirate/radarr/)
+* [Mylar](https://github.com/evilhero/mylar)
+* [Lazy Librarian](/recipies/autopirate/lazylibrarian/)
+* Headphones (this page)
+* [NZBHydra](/recipies/autopirate/nzbhydra/)
+* [Ombi](/recipies/autopirate/ombi/)
+* [Jackett](/recipies/autopirate/jackett/)
+* [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? 💬