[Query] - config.yaml Formatting Changes
Good evening matey,
Getting around to converting from v1 to v2 and editing the config.yaml in Windows VS Code. It keeps coming up with an error of Nested Mappings are not allowed in compact mappings. Implicit keys need to be on a single line.
Copilot deoided to make some changes in adding in "enabled:" to each section and this seems to still be recognised during startup. I wasn't sure whether you were interested in the changes at all, just made it easier to understand for me to be able to enable / disable the sections of the program.
Hi there
Thank you for reporting this.
If understand you correctly, thats an interesting behavior difference between linux & windows it seems.
On config.yaml on linux:
Jobname: will enable the job with default settings
Thus it‘s a handy short notation and you dont have to say that it‘s enabled. If the job isn‘t specified, it‘s disabled.
I don‘t use windows, if you or somebody wants to figure out how to also make it work on windows, please feel free to create a PR :)
Having issues converting docker compose from V1 to V2. Receiving an error stating services.decluttarr additional properties 'SONARR', 'RADARR', 'QBITTORRENT' not allowed
decluttarr: network_mode: host image: ghcr.io/manimatter/decluttarr:latest restart: unless-stopped environment: - TZ=America/New_York - LOG_LEVEL=VERBOSE - TIMER=30 - REMOVE_FAILED_DOWNLOADS=True - REMOVE_FAILED_IMPORTS=True - REMOVE_METADATA_MISSING=True - REMOVE_MISSING_FILES=True - REMOVE_ORPHANS=True - REMOVE_SLOW=True - REMOVE_STALLED=True - REMOVE_UNMONITORED=True - MAX_STRIKES=48 - MIN_SPEED=3 radarr: - BASE_URL=http://localhost:7878 - API_KEY=${RADARR_API_KEY} sonarr: - BASE_URL=http://localhost:8989 - API_KEY=${SONARR_API_KEY} qbittorrent: - BASE_URL=http://localhost:8081 - USERNAME=${TORRENT_USER} - PASSWORD=${TORRENT_PASSWORD}
Are you missing the „>“? See in readme:
SONARR: > - base_url: "http://sonarr1:8989" api_key: "$SONARR_API
I did see that and I did try that, but regardless of what I do it fails with the same message.
Please can you create a separate issue. Are you using linux?
Hey matey,
The config.txt and example_config.txt files I linked are working for me on my system and I've got no dramas with it so far. Do you still want me to do a PR?
Hey @MrBogger -- Not sure I understand what you are suggesting to include in your PR. The "enabled" setting also works with the "config.yaml"
I think the only thing that doesn't seem to work is that the "enabled: true" can be left away, whilst still providing just the job name (ie which translates to an empty dictionary for this job)
Example:
search_missing:
For decluttarr, the above is equivalent to
search_missing:
enabled: true
And the absence of search_missing: is equivalent to
search_missing:
enabled: false
the above are equivalent on Linux, but it seems that the former doesn't properly work on windows. Are you suggesting to fix that for windows? The second should already work now.