Environment variables¶

Advanced reference for process / container wiring and legacy Settings fallbacks. Most day-to-day tunables live in the Settings UI (SQLite).

Container / entrypoint¶

Frontend (Node)¶

SERVICE_PROVIDER since 0.10.0¶

Hosted InfiniDysk services can identify the service provider and mark selected navigation destinations as unavailable. Disabled destinations remain visible in the sidebar; selecting one explains that the feature is disabled by the provider and links to the provider's support page (or website). The provider attribution also appears in the page footer.

Set SERVICE_PROVIDER to a JSON object on the frontend process:

environment:
  SERVICE_PROVIDER: >-
    {"name":"ElfHosted","url":"https://elfhosted.com","supportUrl":"https://docs.elfhosted.com","disabledFeatures":["watchtower","search","settings.indexers","settings.profiles","settings.watchtower","settings.warden","settings.rclone"]}

The object requires:

• name: service provider name shown in the dialog and footer
• url: provider website using http or https (used in the footer link)
• disabledFeatures: navigation identifiers to make unavailable

Optional:

• supportUrl: support page using http or https, used for the "Contact" link in the disabled-feature dialog; falls back to url when omitted

Top-level navigation identifiers are overview, queue, watchdog, watchtower, explore, health, logs, and search. overview cannot be disabled — it is the app's landing page and the fallback destination when closing the "feature not available" dialog, so it always stays reachable.

Settings navigation identifiers are settings.usenet, settings.indexers, settings.profiles, settings.watchdog, settings.preflight, settings.watchtower, settings.warden, settings.sabnzbd, settings.webdav, settings.arrs, settings.repairs, settings.rclone, settings.maintenance, settings.backup, and settings.support.

This controls frontend presentation only. Providers must separately configure or restrict backend capabilities when enforcement is required.

Backend (.NET)¶

PORT and ASPNETCORE_URLS control listeners inside the container; they do not change Docker's published host port. For normal Compose deployments, leave the internal ports unchanged and use a HOST_PORT:CONTAINER_PORT mapping. See Change the published port for bridge networking, host networking, healthcheck, and DUMB examples.

Settings fallbacks (when UI empty)¶

These apply only when the matching Settings value is empty and no NZBDAV_CONFIG__... overlay supplies that key.

Example Compose snippet¶

Operational wiring only — for a full Settings-via-ENV stack see the headless Compose example.

environment:
  PUID: "1000"
  PGID: "1000"
  TZ: America/New_York
  TRUST_PROXY: "1"
  SECURE_COOKIES: "true"
  TRUSTED_INTERNAL_HOSTS: "prowlarr"