If provided parameter already set through config file, cli/env parameter should take precedence to avoid locking yourself out of UI due to misconfiguration. These parameters might be set using either command line arguments or environment variables. I'd like to get an ability to change some essential configuration parameters, which should be accessible outside of configuration UI. For that you should open UI (which is slow), navigate to General settings (which is slow), change configuration and save (which is slow.
![sonarr config file sonarr config file](https://forums-sonarr-tv.s3.dualstack.us-east-1.amazonaws.com/optimized/2X/7/7843328e2c5959657ae4da5ea7ae0136b0138946_2_1035x646.jpeg)
To investigate an issue I needed to change log level. It takes couple of minutes to load UI and switch between pages.
#SONARR CONFIG FILE MANUAL#
It restricts you from automating deploys because you can't change connection parameters without manual intervention.Passing files inside docker volumes also isn't easy task Due to limited access to container filesystem it's also very inconvenient to manually edit config.xml because slim images don't even have text editor inside.UI is inaccessible and because you can't access UI to change base URL and you can't change base URL without accessing UI.Sonar itself isn't exposed behind bridge network. I set up Sonarr behind reverse proxy on dedicated path inside Docker.While working on Sonarr installation I had major blocking issues caused by inability to change configuration without using UI or manually editing config.xml: Is your feature request related to a problem? Please describe