Update for leanpub preview

manuscript/recipes/autopirate/radarr.mde

@@ -0,0 +1,91 @@
+!!! 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.
+
+# Radarr
+
+
+[Radarr](https://radarr.video/) is a tool for finding, downloading and managing movies. Features include:
+
+* Adding new movies with lots of information, such as trailers, ratings, etc.
+* Can watch for better quality of the movies you have and do an automatic upgrade. eg. from DVD to Blu-Ray
+* Automatic failed download handling will try another release if one fails
+* Manual search so you can pick any release or to see why a release was not downloaded automatically
+* Full integration with SABnzbd and NZBGet
+* Automatically searching for releases as well as RSS Sync
+* Automatically importing downloaded movies
+* Recognizing Special Editions, Director's Cut, etc.
+* Identifying releases with hardcoded subs
+* Importing movies from various online sources, such as IMDb Watchlists (A complete list can be found here)
+* Full integration with Kodi, Plex (notification, library update)
+* And a beautiful UI
+* Importing Metadata such as trailers or subtitles
+
+![Radarr Screenshot](../../images/radarr.png)
+
+!!! tip "Sponsored Project"
+    Sonarr is one of my [sponsored projects](/sponsored-projects/) - a project I financially support on a regular basis because of its utility to me. I forget it's there until I (reliably) receive an email with new and exciting updates 😁
+
+## Inclusion into AutoPirate
+
+To include Radarr in your [AutoPirate](/recipes/autopirate/) stack, include the following in your autopirate.yml stack definition file:
+
+```
+radarr:
+  image: linuxserver/radarr:latest
+  env_file : /var/data/config/autopirate/radarr.env
+  volumes:
+   - /var/data/autopirate/radarr:/config
+   - /var/data/media:/media
+  networks:
+  - internal
+
+radarr_proxy:
+  image: a5huynh/oauth2_proxy
+  env_file : /var/data/config/autopirate/radarr.env
+  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``` 👍
+
+## 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](/recipes/autopirate/sabnzbd.md)
+* [NZBGet](/recipes/autopirate/nzbget.md)
+* [RTorrent](/recipes/autopirate/rtorrent/)
+* [Sonarr](/recipes/autopirate/sonarr/)
+* Radarr (this page)
+* [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)
+
+
+## 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.