You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using buildarr would allow setup services to integrate with each other upon
activation with no user input, definitely nice.
Doesn't have support for all the *Arrs, not even the upcoming SonarrV4, and it hasn't been updated for some months.
Needs to be added to nixpkgs, not too hard, but is not worth it if the
project is abandoned.
Package with nix
Add to nixpkgs
In the ideal case, buildarr would run only once after initial build to
avoid overwriting user configuration. Otherwise overwriting should be okay,
as the buildarr configuration is designed to be lean. I would possibly also
like to expose the buildarr configuration using extraSettings, but the
setup is the main desired feature here.
Sonarr
Setup media directory
Add Transmission
Set hard linking
Readarr
Setup media directory
Add Transmission
Set hard linking
Lidarr
Setup media directory
Add Transmission
Set hard linking
Readarr
Setup media directory
Add Transmission
Set hard linking
Prowlarr
Setup integration with enabled "*Arrs"
Set hard linking
The text was updated successfully, but these errors were encountered:
It seems buildarr will be maintained, and that lidarr/readarr support is on the table. So this could be worth pursuing once SonarrV4 support is implemented in buildarr.
Unfortunately, Buildarr seems to just not be there yet in terms of support for the programs that Nixarr supports, and would therefore be unwise to add in their current form. Specifically, Buildarr does not even support SonarrV4 yet, which would definitely be necessary for Buildarr support to be added, furthermore, Buildarr should also support Lidarr and Readarr. See this issue for more details.
Using buildarr would allow setup services to integrate with each other upon
activation with no user input, definitely nice.
Doesn't have support for all the *Arrs, not even the upcoming SonarrV4, and it hasn't been updated for some months.
Needs to be added to nixpkgs, not too hard, but is not worth it if the
project is abandoned.
In the ideal case, buildarr would run only once after initial build to
avoid overwriting user configuration. Otherwise overwriting should be okay,
as the buildarr configuration is designed to be lean. I would possibly also
like to expose the buildarr configuration using
extraSettings
, but thesetup is the main desired feature here.
The text was updated successfully, but these errors were encountered: