Flemmarr VS buildarr

The arr stack has api for each product so setting them from a config file is possible. I use flemarr for this. Writting the file the way you want can be tideous but once you get it right you can reproduce your setup so much quicker

Define configuration of all instances in a single configuration file in a well-defined format. Similar to Flemmarr, but instead of using API keys and values as-is, defines a configuration interface that is easier to define by hand.

Maybe check out https://github.com/Flemmarr/Flemmarr which could help configure the newly setup services automatically. I'm also working on some improvements for it in the background :).

Can't go into details right now, but how is it different from Flemarr ?

Introducing Flemmarr, a little script packaged in a Docker image that you can simply add to your docker-compose.yml to apply a static config file.

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.