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.
RTorrent / ruTorrent¶
Choose incoming port¶
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 ruTorrent in your AutoPirate stack, include the following in your autopirate.yml stack definition file:
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 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
I automatically and instantly share (with my sponsors) a private "premix" git repository, which includes necessary docker-compose and env files for all published recipes. This means that sponsors can launch any recipe with just a
git pull and a
docker stack deploy 👍.
🚀 Update: Premix now includes an ansible playbook, so that sponsors can deploy an entire stack + recipes, with a single ansible command! (more here)
Assemble more tools..¶
Continue through the list of tools below, adding whichever tools your want to use, and finishing with the end section:
- RTorrent (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 (sponsor) 👏¶
Did you receive excellent service? Want to make your waiter happy? (..and support development of current and future recipes!) Sponsor me on Github / Patreon, or see the contribute page for more (free or paid) ways to say thank you! 👏
Flirt with waiter (subscribe) 💌¶
Want to know now when this recipe gets updated, or when future recipes are added? Subscribe to the RSS feed, or leave your email address below, and we'll keep you updated. (*double-opt-in, no monkey business, no spam)