releasecue/releasecue-connect repository overview

⁠ReleaseCue Connect

ReleaseCue Connect securely links Radarr, Sonarr, Plex, Jellyfin, and Emby on your home network to your ReleaseCue account.

It uses outbound HTTPS only. No inbound ports, VPN, port forwarding, or public service URLs are required. Local service credentials and private addresses remain inside the container.

⁠Requirements

• Docker with Docker Compose
• An active ReleaseCue Pro account
• Radarr, Sonarr, Plex, Jellyfin, or Emby

Images support linux/amd64 and linux/arm64.

⁠Quick start

Create a directory:

mkdir releasecue-connect
cd releasecue-connect

Create compose.yml:

services:
  releasecue-connect:
    image: releasecue/releasecue-connect:latest
    pull_policy: always
    restart: unless-stopped
    read_only: true
    cap_drop:
      - ALL
    security_opt:
      - no-new-privileges:true
    volumes:
      - ./config.json:/config/config.json:ro
      - releasecue-connect-data:/data

volumes:
  releasecue-connect-data:

Create config.json:

{
  "name": "Home Server",
  "releaseCueUrl": "https://releasecue.com",
  "services": [
    {
      "id": "radarr-main",
      "type": "radarr",
      "label": "Radarr",
      "url": "http://radarr:7878",
      "apiKey": "YOUR_RADARR_API_KEY"
    },
    {
      "id": "sonarr-main",
      "type": "sonarr",
      "label": "Sonarr",
      "url": "http://sonarr:8989",
      "apiKey": "YOUR_SONARR_API_KEY"
    },
    {
      "id": "plex-main",
      "type": "plex",
      "label": "Plex",
      "url": "http://plex:32400",
      "token": "YOUR_PLEX_TOKEN"
    }
  ]
}

Only include services you use. The configured service URLs must be reachable from inside the container.

Start ReleaseCue Connect:

docker compose up -d
docker compose logs -f releasecue-connect

On its first run, the container displays a one-time pairing URL and code.

Approve it in:

• ReleaseCue app: Server → ReleaseCue Connect
• ReleaseCue website: Settings → ReleaseCue Connect

After pairing, synchronization begins automatically.

⁠Updating

docker compose pull
docker compose up -d

Your pairing credential and synchronization state remain in the Docker volume.

⁠Service configuration

⁠Radarr or Sonarr

{
  "id": "sonarr-main",
  "type": "sonarr",
  "label": "Sonarr",
  "url": "http://sonarr:8989",
  "apiKey": "YOUR_API_KEY"
}

⁠Plex

{
  "id": "plex-main",
  "type": "plex",
  "label": "Plex",
  "url": "http://plex:32400",
  "token": "YOUR_PLEX_TOKEN"
}

⁠Jellyfin or Emby

{
  "id": "jellyfin-main",
  "type": "jellyfin",
  "label": "Jellyfin",
  "url": "http://jellyfin:8096",
  "token": "YOUR_API_KEY",
  "userId": "YOUR_USER_ID"
}

Service IDs must remain unique and stable. Changing an ID causes ReleaseCue to treat it as a new service.

⁠What is synchronized

Depending on the service, ReleaseCue Connect synchronizes:

• Service availability and health
• Radarr and Sonarr library status
• Missing and cutoff-unmet items
• Download queues
• Upcoming monitored releases
• Plex, Jellyfin, and Emby watch status
• Commands initiated from ReleaseCue, including adding or searching for titles

Local API keys, access tokens, private URLs, filesystem paths, download names, and raw service responses are not uploaded.

⁠Security

The recommended container configuration:

• Exposes no ports
• Uses outbound HTTPS only
• Runs as an unprivileged user
• Uses a read-only root filesystem
• Drops all Linux capabilities
• Enables no-new-privileges
• Mounts config.json read-only

Keep config.json private and never commit it to source control.

⁠Support

Website: releasecue.com⁠