![]() ![]() NZBGet (nzb download client, configure nzb newhosting site, Radarr, Sonarr, Lidarr point NZBGet to download content. ![]() ![]() Prowlarr (Configure your torrent/usenet indexers, Radarr, Sonarr, Lidarr point to Prowlarr). Overserr (Allows users to request content). Plex (Media Content Manager, desktop, mobile, tv apps. Allow webseed URLs when creating torrents in transmission-create Display more progress information during torrent creation in transmission-create Everything Else. Updated Qt CMakeLists.txt to include support for building svg. I might be mixing up some terms there, but that setup has made downloading content so much easier and quicker. Open transmission -> preferences -> peers Paste the URL into the URL bar and click update (the download should be visible) On the mac finder bar (no program selected) click on go -> go to folder Enter /Library/Application Support/Transmission Select the blocklist folder (notice that there is only one blocklist. Added Qt dependencies for Windows build instructions and minor fixes. Everything is spun up in docker using the linuxserverio images. Have to pay for a decent news hosting and indexer, but after some tweaking you can download new releases so much quicker without worrying about vpns and ratios.Īt this point I have Plex and Overseer hooked up to Prowlarr, Sonarr, Lidarr and Radarr, with Prowlarr connected to my nzb client and server (it was easy to cut over from transmission, using the secure ports to talk the news hosting and client accounts). If you want quicker speeds, look into usenet. Such codebases will make any attempts at refactoring unsafe and inherently stressful, that's what I meant with brittle - you'll never be able to change anything whilst having confidence that things won't break all over the place. The worst cases are where you don't have the tests and things break in ways that might not be immediately obvious. Sure, however tests failing after refactoring or removing seemingly unused bits of code will be a great way to figure out when one's assumptions about how everything works are mistaken, or to discover bits of code that one wasn't even aware of.Īlong the lines of: "Oh hey, our tests caught that removing this seemingly unused dependency from pom.xml will break PDF export logic, because for some reason it loads classes dynamically and needs that package" or maybe "The tests revealed that our latest refactoring breaks JSON serialization of dates, because while we should be able to use these annotations for our Dtos properly, the underlying framework gets confused because of our serialization library." Tests can help reveal when those types of dependencies break, but even so, I would argue that is brittle code held together with cling wrap. ![]()
0 Comments
Leave a Reply. |