Mylar3 in Autopirate Docker Swarm stack
Get your FREE "elfhosted" Mylar instance for demo / trial
Want to see a live demo, or "kick the tyres" before you commit to self-hosting Mylar?
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.
Mylar is a tool for downloading and managing digital comic books.
Inclusion into AutoPirate
To include Mylar in your AutoPirate stack, include something like the following example in your
autopirate.yml docker-compose v3 stack definition file:
mylar: image: lscr.io/linuxserver/mylar3:latest env_file : /var/data/config/autopirate/mylar.env volumes: - /var/data/autopirate/mylar:/config - /var/data/media:/media networks: - internal deploy: labels: # traefik - traefik.enable=true - traefik.docker.network=traefik_public # traefikv1 - traefik.frontend.rule=Host:mylar.example.com - traefik.port=8090 - traefik.frontend.auth.forward.address=http://traefik-forward-auth:4181 - traefik.frontend.auth.forward.authResponseHeaders=X-Forwarded-User - traefik.frontend.auth.forward.trustForwardHeader=true # traefikv2 - "traefik.http.routers.mylar.rule=Host(`mylar.example.com`)" - "traefik.http.routers.mylar.entrypoints=https" - "traefik.http.services.mylar.loadbalancer.server.port=8090" - "traefik.http.routers.mylar.middlewares=forward-auth"
Fast-track with premix! 🚀
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:
- 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 compliment the chef? (..and support development of current and future recipes!) Sponsor me on Github / Ko-Fi / Patreon, or see the contribute page for more (free or paid) ways to say thank you! 👏
Employ your chef (engage) 🤝
Is this too much of a geeky PITA? Do you just want results, stat? I do this for a living - I'm a full-time Kubernetes contractor, providing consulting and engineering expertise to businesses needing short-term, short-notice support in the cloud-native space, including AWS/Azure/GKE, Kubernetes, CI/CD and automation.
Learn more about working with me here.
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.
Your comments? 💬
[^2]. If you intend to configure Mylar to perform its own NZB searches and push the hits to a downloader such as SABnzbd, then in addition to configuring the connection to SAB with host, port and api key, you will need to set the parameter
host_return parameter to the fully qualified Mylar address (e.g.