Sonarr is a smart PVR for newsgroup and bittorrent users.
This service requires the following other services:
- a Traefik reverse-proxy server
To enable this service, add the following configuration to your vars.yml file and re-run the installation process:
########################################################################
# #
# sonarr #
# #
########################################################################
sonarr_enabled: true
sonarr_hostname: sonarr.example.com
# To mount additional data directories, use `sonarr_container_additional_volumes`
#
# Example:
# sonarr_container_additional_volumes:
# - type: bind
# src: /path/on/the/host
# dst: /data
# - type: bind
# src: /another-path/on/the/host
# dst: /read-only
# options: readonly
########################################################################
# #
# /sonarr #
# #
########################################################################In the example configuration above, we configure the service to be hosted at https://sonarr.example.com.
A sonarr_path_prefix variable can be adjusted to host under a subpath (e.g. sonarr_path_prefix: /sonarr), but this hasn't been tested yet.
After installation, you should access your new Sonarr instance at the URL you've chosen and configure a username and password. The recommended authenticaton method is Forms (Login Page).
For additional configuration options, refer to ansible-role-sonarr's defaults/main.yml file.
Consider these other supported services that are also in the *Arr stack of media automation tools:
- Radarr
- Jackett
- For Jackett integration instructions, see the setup guide
- qBittorrent
- For qBittorrent integration instructions, see the setup guide
- Overseerr