Whisparr (Core Service)#

Whisparr is an automation tool for managing adult content libraries, similar to Radarr/Sonarr workflows.

Service Relationships#

Configuration in dumb_config.json#

"whisparr": {
  "instances": {
    "Default": {
      "enabled": false,
      "whisparr_version": "",
      "core_service": "",
      "use_neutarr": false,
      "postgres_enabled": false,
      "postgres_main_db": "",
      "postgres_log_db": "",
      "process_name": "Whisparr",
      "repo_owner": "Whisparr",
      "repo_name": "Whisparr",
      "release_version_enabled": false,
      "release_version": "latest",
      "branch_enabled": false,
      "branch": "",
      "commit_sha": "",
      "clear_on_update": false,
      "exclude_dirs": [],
      "platforms": [],
      "suppress_logging": false,
      "auto_update": false,
      "auto_update_interval": 24,
      "auto_update_start_time": "04:00",
      "pinned_version": "",
      "port": 6969,
      "config_dir": "/whisparr/default",
      "config_file": "/whisparr/default/config.xml",
      "log_file": "/whisparr/default/logs/whisparr.txt",
      "command": [],
      "env": {}
    }
  }
}

Key Configuration Fields#

• whisparr_version: Choose v2 or v3 (Eros), or leave blank to detect and preserve the existing version. A new instance with no existing version defaults to v2.
• core_service: Set to decypharr, infinidysk, altmount, or a list of workflow keys to enable DUMB integration.
• use_neutarr: Opt this instance into NeutArr automation.
• postgres_enabled: Opt this instance into DUMB-managed PostgreSQL config. SQLite is the default; set this to true only when you want Whisparr to use PostgreSQL.
• postgres_main_db / postgres_log_db: Optional database-name overrides. When blank, DUMB uses whisparr-main and whisparr-log for the default instance, or unique instance-scoped names for additional instances.
• port: Web UI port (default 6969).
• pinned_version: Optional exact numeric release version, such as 3.6.4.1865, within the selected major version. This applies when release_version_enabled is false.
• repo_owner / repo_name: GitHub release source. Official v2 releases use Whisparr/Whisparr; v3 releases use Whisparr/Whisparr-Eros.
• release_version_enabled / release_version: Select a GitHub release using latest, prerelease, or an exact tag. When disabled, an unpinned instance still installs the latest official release for its selected version.
• branch_enabled / branch: Select an update channel: v2 or v2-develop for v2, and eros or eros-develop for v3. These select packaged releases; Whisparr source builds are not supported.
• commit_sha: Leave blank. Installing Whisparr from a specific source commit is not supported.
• clear_on_update / exclude_dirs: Generic install-cleanup settings. Whisparr stages a replacement of its managed binary directory; keep config_dir separate from that directory. These fields do not convert or relocate databases.
• config_dir, config_file, log_file: Paths for config and logs.

Choosing v2 or v3 (Eros)#

Choose Whisparr v2, Whisparr v3 (Eros), or Detect existing version during onboarding. You can also set whisparr_version on the instance in DUMB Config.

Leaving the setting blank preserves the version indicated by the existing database, installed binary, repository, or update channel. It defaults to v2 only for a new instance without that existing version information.

Both versions use logs.db for SQLite logs. DUMB keeps each instance's binary separate under /opt/whisparr/instances/<instance-slug>/Whisparr/Whisparr and leaves the configured data directory in place.

For example, a separate v3 instance using the official stable releases can use:

"whisparr": {
  "instances": {
    "Eros": {
      "enabled": true,
      "whisparr_version": "v3",
      "repo_owner": "Whisparr",
      "repo_name": "Whisparr-Eros",
      "release_version_enabled": true,
      "release_version": "latest",
      "port": 6970,
      "config_dir": "/whisparr/eros",
      "config_file": "/whisparr/eros/config.xml",
      "log_file": "/whisparr/eros/logs/whisparr.txt"
    }
  }
}

PostgreSQL database mode#

When postgres_enabled is true, DUMB:

• enables the bundled PostgreSQL service if needed;
• creates the Whisparr main/log databases in postgres.databases;
• starts PostgreSQL before Whisparr; and
• writes the required PostgresUser, PostgresPassword, PostgresHost, PostgresPort, PostgresMainDb, and PostgresLogDb entries to Whisparr's config.xml.

During onboarding, enabling postgres_enabled for Whisparr is enough; you do not need to separately select PostgreSQL as an optional service.

For an existing instance, use Database Migration on the service page. DUMB requires a rehearsal, initializes an isolated Whisparr-owned PostgreSQL schema, imports and validates every table, and preserves SQLite for rollback. See SQLite to PostgreSQL Migration.

This changes the database backend for the installed Whisparr version. It does not convert a v2 library into a v3 library.

Repo-based installs and updates#

DUMB installs ready-to-run official GitHub release archives for the selected Whisparr version. The default install and updater also use these archives; older Servarr nightly and eros download feeds are not used to find current Whisparr releases.

• Default stable releases: Leave release_version_enabled: false and pinned_version blank.
• Explicit GitHub release: Set release_version_enabled: true with the matching official repository, then choose latest, prerelease, or a release tag in release_version.
• Exact numeric pin: Leave release_version_enabled: false and set pinned_version to the exact release version from the selected major version.
• Development channel: Use v2-develop or eros-develop with branch_enabled: true. Use the corresponding stable channel to stay on stable releases.

An explicit GitHub release selection takes priority over pinned_version. Release tags and pins must match the selected Whisparr major version. Unavailable releases fail the install or update instead of silently switching versions or compiling from source.

Updates replace the managed binary directory after staging the selected release. Configuration and database directories remain separate, and DUMB checks their compatibility before stopping the running service or activating a replacement binary.

Integration with DUMB#

• For Decypharr integration, set core_service to decypharr and follow the Decypharr guide.
• For InfiniDysk integration, set core_service to infinidysk and follow the InfiniDysk guide.
• For AltMount integration, set core_service to altmount and follow the AltMount guide.
• For combined workflows, set core_service to a list such as ["decypharr", "infinidysk", "altmount"].
• Use Prowlarr to centrally manage indexers and sync them to Whisparr.
• DUMB enables Arr folder permission updates and applies permissions to configured root folders during integration.
• See Core Service Routing for how core_service affects automation.

Accessing the UI#

• Navigate to: http://<host>:6969

Resources#

• Whisparr Website
• Whisparr GitHub
• Whisparr v2 releases
• Whisparr v3 (Eros) GitHub
• Whisparr v3 (Eros) releases
• Whisparr PostgreSQL setup