This is not a complete recipe - it's a component of the AutoPirate "uber-recipe", but has been split into its own page to reduce complexity.
NZBGet performs the same function as SABnzbd (downloading content from Usenet servers), but it's lightweight and fast(er), written in C++ (as opposed to Python).
Inclusion into AutoPirate¶
I share (with my patreon patrons) 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 👍
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
nzbget: image: linuxserver/nzbget env_file : /var/data/config/autopirate/nzbget.env volumes: - /var/data/autopirate/nzbget:/config - /var/data/media:/data networks: - internal nzbget_proxy: image: a5huynh/oauth2_proxy env_file : /var/data/config/autopirate/nzbget.env 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
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.
Assemble more tools..¶
Continue through the list of tools below, adding whichever tools your want to use, and finishing with the end section:
- NZBGet (this page)
- Lazy Librarian
- End (launch the stack)
Chef's Notes 📓¶
- 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.
Tip your waiter (support me) 👏¶
Did you receive excellent service? Want to make your waiter happy? (..and support development of current and future recipes!) See the support page for (free or paid) ways to say thank you! 👏