I think visually so this didn’t take me long todo, but just start slapping stuff down into a notepad and drawing lines, then use obsidian or a flow chart tool to do what I did. Afterwards it helped me a lot by making sure my torrents and nzbs don’t get any hiccups when implementing a new feature (like switch games)
I auto-upload to trackers that allow it. Instead of having the torrent already in qBit, I have autobrr send it to qbit with a special filter that checks for my username on the trackers I upload to.
I do this because If I grab the torrent at the same time as all the leechers then there’s no delay for the leechers to start downloading meaning they don’t have to re-poll the tracker as much to find me (the seeder)
This also works better for if you’re not a pre-approved uploader (someone who doesn’t need moderator approval to upload). That way once your torrent is approved I can start seeding right away.
Same, but I was on the grind for a BHD invite and by time I got it, my trackers list was 10+ and found having automation better then manually upkeeping on everything.
Haha thanks, Obsidian has been my study friend for a while and what I write all my modding guides in. Seeing how much people liked this post, I plan to post my full guides now too onto here :3
I did try both actually, I just didn’t enjoy adding another service for people to use, it was too difficult convincing them to use another site and/or app. I just settled for the plex sync that way people don’t even have to touch ombi at all. Everything they need for media is contained in plex.
I admit though I bet for others ombi and overseerr are great, as they are great projects, just wasn’t a fit for me sadly :/
Couldn’t have said it much better myself. I think of hardlinks like backend and front end development offices.
The backend team has the data that frontend teams 1 & 2 use, but frontend team 3 isn’t in the same office (filesystem) as the backend team so they can’t access the data.
If frontend team 2 goes down, frontend team 1 still has access to the backend’s data
Writing new data: teams 1 and 2 go down then fuckit we can bulldoze backend and make a new backend for any new frontend teams.
No weekly manga anywhere. The closes I got was monitoring AnimeBytes for manga updates via Autobrr. Since AnimeBytes only keeps the most complete pack of each manga. So when a new chapter/volume is released the old torrent gets deleted and new one is made. So that keeps things easy for adding content… but not removing content to avoid duplicate volumes.