Skip to content

Getting started

Docs track latest

These pages describe the latest InfiniDysk release. Features and settings marked with a since 0.8.0 pill (or similar) need at least that version — check your image tag or Settings → About before following a new workflow.

Choose a path based on where you are:

  • Install with Docker

    Persistent Compose deploy, health checks, reverse-proxy notes.

    Docker

  • Migrate from another build

    Official path from nzbdav-dev v0.6.4, plus community forks (Pukabyte, NzbDavEx).

    Migration

  • First run

    New installs continue from account creation; existing installs open the guide after the first administrator login following upgrade.

    First run · Setup Guide

  • Connect *Arr

    Add InfiniDysk as a SABnzbd download client in Sonarr and Radarr.

    Connect Radarr/Sonarr

  • Understand the flow

    How queue → mount → stream works with media servers.

    Architecture

Prerequisites

  1. Usenet provider — NNTP host, credentials, and connection allowance.
  2. Indexers (optional for first play) — Newznab-compatible sources for search and *Arr.
  3. Docker — Engine + Compose v2. Symlink imports also need Linux FUSE (/dev/fuse).

Setup and hosting options

Option Who it’s for Start here
Self-hosted Docker You run Compose (or Unraid/etc.) and wire *Arr / rclone yourself Docker
DUMB (Debrid Unlimited Media Bridge) You want InfiniDysk as a fully supported core module with guided onboarding and Arr wiring InfiniDysk on dumbarr.com

DUMB treats InfiniDysk as a first-class Usenet WebDAV / SABnzbd-compatible workflow service (core_service: nzbdav), including automatic Arr download-client and symlink-path integration when you select it during onboarding. Prefer DUMB’s own docs for stack-specific paths and ports; use this site for InfiniDysk Settings, features, and troubleshooting.

Release channels and tags

Docker images and prebuilt Linux archives follow the same release train. Choose a tag based on how much change you want to absorb:

Tag Definition
latest The current stable release — the same definition as any project. Recommended for most deployments.
lts A curated stable pointer that generally trails latest by a few minor/patch releases, for operators who prefer the front lines to do the testing. Docker image tag only; promoted manually, not on every release.
rc Release candidate for the upcoming version, promoted from dev builds after basic regression testing. Preferred for all but the most daring testers. Published to ghcr.io/infinidysk/infinidysk only, not Docker Hub or the legacy path.
dev Work-in-progress snapshots deployed to the maintainer’s non-production instance to validate basic functionality. Expect a noisy tag: frequent, sometimes non-functional builds, with no per-build version numbers. Testing only. Published to ghcr.io/infinidysk/infinidysk and Docker Hub, but not the legacy path.

For reproducible deployments, pin an exact version tag (v1.2.3) or a rolling minor/major alias (v1.2, v1). Versioned v*-rc.* pre-releases and image tags are removed when the stable release ships; the rolling rc and dev tags persist.

Building from source

Cloning the repository and running from source remains possible — see Contributing — but it is a development workflow, not a supported deployment method. Releases are tested as the published Docker image and prebuilt Linux archives; source builds are not part of release testing.

After install

Goal Next
Plex + symlinks Import strategies → Mounting WebDAV
Emby/Jellyfin + STRM Import strategies → Media servers
Stremio on demand Stremio
Tune Settings Configuration