Having started out in the world of Napster & Limewire, I’ve always relied on public sources. It wasn’t until in the early '10s that I lucked into a Gazelle-based tracker that was started by some fellow community members. Unfortunately, I wasn’t paying enough attention when they closed shop and didn’t know how to move elsewhere. Combined with some life circumstances I gave up the pursuit for the time being.
It wasn’t until recently that a friend was kind enough to help me get back and introduced me to current state of automation. Over the course of a few months, I’ve since built up the attached systems. I’ve been having an absolute blast learning and am very impressed with all of the contributions!
After all of the updates due to BF deals, I put together the attached diagram as it was starting to get too complex to keep all of the interactions in my head. 😅
Setup
All of the services run in Docker containers.
Each container is a separate Compose file managed by Systemd.
The system itself is in a VM running on my home server (both Arch, btw).
Tailscale is used for remote access to the local network.
ProtonVPN is managed by Gluetun and uses a separate network for isolating services.
Questions
What am I missing or can be improved?
Is there a better way to document?
What do you do differently that might be beneficial?
Thoughts
I had Calibre set up at one point, but I really don’t like how it tracks files by renaming them. I have been considering trying to automate with the CLI instead, but haven’t gotten around to it yet.
I’ve been toying with the idea of creating a file-arr for analyzing disk usage, performing common operations, and exposing a web-based upload/download client so I don’t have to mount the volume everywhere.
Similarly, I’m interested in a way to aggregate logs/notifications/metrics. I’m aware of Notifiarr, but would prefer a self-hosted version.
I just set up Last FM scrobbling so I don’t have any data yet. I’m hoping to use that for discovery and if possible, playlist syncing or auto-generation.
Notes
Diagram was made using D2lang.
Some of the connections have been simplified to improve readability / routing.
Some services have been redacted out of an abundance of caution.
I know VPN with Usenet isn’t necessary, but it’s easier to keep it consistent.
Also, thanks for the recommendations to check out deemix/Deezer. That worked really well! 😀
The systemd.timers are basically cronjobs for scripts I wrote to address a few of the pain points I’ve encountered with the setup. They’re either simple curl or wget and jq calls or use Python for more complex logic. The rest are services that are either a part of or adjacent to *arrs.
As for k8s, personally I feel that would add more complexity than it’s worth. I’m not looking for a second job. 😛
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
The
systemd.timersare basically cronjobs for scripts I wrote to address a few of the pain points I’ve encountered with the setup. They’re either simplecurlorwgetandjqcalls or use Python for more complex logic. The rest are services that are either a part of or adjacent to *arrs.As for k8s, personally I feel that would add more complexity than it’s worth. I’m not looking for a second job. 😛
“But Kubernetes will simplify everything!!!1”
🤷♂️
I mean all problems are solved with another layer of abstraction right?
We need to go deeper