Each service is a separate docker-compose.yml, but they are more-or-less the same as the example configs provided by each service. I did it this way as opposed to a single file to make it easier to add/remove services following this pattern.
I do have a higher quality version of the diagram, but had to downsize it a lot to get pictrs to accept it…
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. 😛
I’m just not confident that I’d be able to pass an interview with either of them. No issue with rules or ratios, I simply don’t have enough time to study up on the technicals. I used to be on a decent tracker years ago, but didn’t pay enough attention when they shut down and missed out on the open invites.
I’ve tried RuTracker in the past but it hasn’t worked very well for me so far. Soulseek sounds interesting, especially if they get a Lidarr integration working.