Skip to content

App Bootstrapping

There are tasks within this playbook that will attempt to automatically configure the connections between supported apps to reduce the amount of time it takes to get up and running.

If a service is no longer enabled, it will be removed from the app connections.

Example: If qBittorrent was enabled when the bootstrap tasks were ran but then you disable qBittorrent, it will remove the download client HMSD - qBittorrent if it exists in Sonarr and Radarr and indexer proxy in Prowlarr if it exists whenever the playbook is ran next.

This requires DNS records to be properly configured for the following apps:

  • Prowlarr

  • Sonarr (including 4K instance if enabled)

  • Radarr (including 4K instance if enabled)

  • Lidarr

By default, the playbook will check for the various apps API keys in their config files.

To enable, set:

inventory/group_vars/all/app_bootstrap.yml
...
hmsdocker_app_bootstrap: true
...

These connections are prefixed with HMSD - and this prefix is required to work correctly. You can modify the settings of the connection, but not the name, otherwise it will just create another.

It will do the following for each service:

  • Prowlarr

    • Configure Indexer Proxies and Tags for the following services (if enabled)

      • FlareSolverr
      • qBittorrent
      • Transmission
      • Deluge
    • Configure the following apps:

      • Sonarr (including 4K)
      • Radarr (including 4K)
      • Lidarr
  • Radarr (including 4K instance if enabled)

    • Configure root folder
    • Configure download clients (if enabled):
      • Transmission
      • qBittorrent
      • Deluge
  • Sonarr (including 4K instance if enabled)

    • Configure root folder
    • Configure download clients (if enabled):
      • Transmission
      • qBittorrent
      • Deluge
  • Lidarr

    • Configure download clients (if enabled):
      • Transmission
      • qBittorrent
      • Deluge

The Seerr apps are unsupported due to requiring you to initially authenticate with Plex after the container first starts and complete setup in order for its API key to work.