recyclarr VS buildarr

Recyclarr (GitHub) to automatically update custom formats per the TRaSH Guides. This took some tweaking to get just right, because it also changed my quality definitions, which I didn't want (YTS releases are fine for most of my users, lol).

(Sidenote - this is so I can utilise Recyclarr to sync profiles and formats from Trash guides - https://github.com/recyclarr/recyclarr)

There's also Recyclarr to automatically sync from the trash guides

[https://github.com/recyclarr/recyclarr.

It's also quite automateable: https://github.com/recyclarr/recyclarr

Capable of using TRaSH-Guides profiles for quality definitions and release profiles, similar to Recyclarr. If the TRaSH-Guides profile is updated, Buildarr will sync those updates to your instances.

I follow the TRaSH Guide, for the most part. I have custom formats set up using Notifiarr, and at this point, either using Notifiarr or Recyclarr custom formats is a necessity for any user. If you don't, your searches with Sonarr and Radarr are going to be all over the place.

I use https://github.com/recyclarr/recyclarr/pkgs/container/recyclarr which loads https://trash-guides.info/.

On point 3, I use Recyclarr to keep my release profiles synced up to Trash's current recommendations.

Then, go through each one, starting from Prowlarr and set them up. Make sure they can talk to each other. Import libraries, adjust what do search for and so on. The biggest hassle is setting up. There are even tools that leverage the APIs for configuration. A rudimentary Infrastructure as Code approach. There is Buildarr and Flemmarr. But for anyone that has already setup their stack, these would be more hassle than help.

I previously posted here a few months ago announcing the first release of Buildarr, a tool intended to be used to express *Arr stack's configuration as code, and automatically applying that configuration without the hassle of using the UI.

If I could suggest a way for anyone with an established Sonarr setup could contribute to Buildarr without actually introducing it to their setup, if anyone could try dumping their Sonarr configuration using the built-in command, and reporting whether it worked or not (along with what types of resources you have configured on your Sonarr) either here or on GitHub, that would be much appreciated.