feat: add Lidarr support#421
Open
korabcenaj wants to merge 2 commits into
Open
Conversation
Allows users to restrict which network interface nzbdav binds to via the LISTEN_ADDRESS environment variable. - Defaults to 0.0.0.0 (all interfaces), preserving existing behaviour - Sets ASPNETCORE_URLS in entrypoint.sh so Kestrel honours the address - Passes LISTEN_ADDRESS to the Node.js frontend server so both processes bind to the same interface - Derives BACKEND_URL from LISTEN_ADDRESS when it is a specific non-loopback/non-wildcard IP - Documents the variable with ENV LISTEN_ADDRESS=0.0.0.0 in Dockerfile and exposes port 8080 alongside the existing 3000 Fixes nzbdav-dev#408
Add Lidarr as a first-class *arr integration alongside Radarr and Sonarr. Backend: - Make ArrClient.BasePath a protected virtual property so subclasses can override it (Lidarr uses /api/v1 instead of /api/v3) - Add LidarrInstances list to ArrConfig and include LidarrClient instances in GetArrClients() / GetInstanceCount() - New LidarrClient: overrides BasePath to /api/v1, implements RemoveAndSearch using artist-path cache + track-file lookup, same caching strategy as SonarrClient - New models: LidarrArtist, LidarrTrackFile, LidarrQueue, LidarrQueueRecord Frontend: - Add LidarrInstances field to ArrConfig interface - Add Add/Remove/Update callbacks for Lidarr instances - Add Lidarr Instances section to the settings UI (between Sonarr and Automatic Queue Management) - Default placeholder port 8686 for Lidarr host field - Include LidarrInstances in isArrsSettingsValid() validation - Update queue management description to mention Lidarr - Update default arr.instances config key to include LidarrInstances ArrMonitoringService automatically monitors Lidarr queues because it calls GetArrClients(), which now returns LidarrClient instances too. Closes nzbdav-dev#284
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #284
Adds Lidarr as a first-class integration alongside the existing Radarr and Sonarr support.
Changes
Backend
ArrClient.csBasePathfromprivate consttoprotected virtualproperty so subclasses can override it (Lidarr uses/api/v1vs/api/v3)ArrConfig.csLidarrInstanceslist; updatedGetArrClients()andGetInstanceCount()LidarrClient.csBasePathto/api/v1; implementsRemoveAndSearchvia artist-path cache + track-file lookup (same caching strategy asSonarrClient)LidarrArtist.csLidarrTrackFile.csLidarrQueue.csLidarrQueueRecord.csArrMonitoringServiceworks automatically — it callsGetArrClients()which now includesLidarrClientinstances, so queue monitoring for Lidarr is included with no further changes.Frontend
LidarrInstancesto theArrConfigTypeScript interfacehttp://localhost:8686for LidarrisArrsSettingsValid()validates Lidarr instances the same way as Radarr/Sonarrarr.instancesconfig value to includeLidarrInstances: []Screenshots
The Lidarr Instances section appears between Sonarr and Automatic Queue Management in the Settings UI, with identical Add/Test/Remove UX.