🎬 Distributed Unlimited Media Bridge 🎬

📜 Description

Distributed Unlimited Media Bridge (DUMB) is an All-In-One (AIO) platform for building and operating a complete automated media stack. It brings together Debrid and Usenet workflows, Arr automation, media servers, request/watchlist tools, service management, logs, metrics, notifications, updates, and embedded service UIs behind a guided setup experience. The maintained container image remains the normal deployment, while the Proxmox Community Scripts integration installs the same controller and managed services natively in an LXC.

DUMB is designed to reduce the glue work that usually comes with multi-service media deployments. You can choose the services that fit your workflow, let DUMB wire the required dependencies, manage them from the DUMB dashboard, and optionally expose selected UIs or public routes through the bundled Traefik access layer.

📦 Projects Included

You are free to use whichever components you like. Not all are required, and some may provide overlapping functionality in different ways.

⚖️ Licensing

DUMB is licensed under GNU GPLv3. Copyright and license notices for third-party components redistributed in the container image are collected in THIRD_PARTY_NOTICES.md. Package-manager and runtime license files are also retained in their standard locations inside the image.

🌟 Features

DUMB provides a guided, single-deployment control plane for configurable media stacks, including:

• Debrid and Usenet workflows, Arr automation, media servers, and request tools
• Service installation, configuration, lifecycle management, logs, health checks, updates, and recovery automation
• Embedded service UIs with optional Traefik and Cloudflare access tooling
• Optional DUMB-managed Authelia identity provider with DUMB and Traefik Proxy Admin OIDC linking plus reusable Traefik ForwardAuth protection
• Metrics, database-health diagnostics, alerts, notifications, and operator migration or repair utilities

This README intentionally keeps the overview brief. See the DUMB Features documentation for the comprehensive capability, configuration, and settings reference.

🐳 Docker Hub

A prebuilt image is hosted on Docker Hub.

🖥️ Proxmox LXC

The Community Scripts helper installs DUMB and its managed services directly in a Debian LXC without Docker. See the Proxmox deployment guide for the recommended all-in-one topology, native paths, updates, backups, and the additional considerations for Plex or Arr applications in other LXCs.

🏷️ GitHub Container Registry

A prebuilt image is hosted on GitHub Container Registry.

🐳 Docker-compose

[!NOTE] The below "ports" section of the compose should be updated based on the service ports used when needing to be exposed. See the below Default Ports Used section for more details

services:
  DUMB:
    container_name: DUMB
    image: iampuid0/dumb:latest
    stop_grace_period: 30s
    shm_size: 128mb
    stdin_open: true
    tty: true
    volumes:
      - /home/username/docker/DUMB/config:/config
      - /home/username/docker/DUMB/log:/log
      - /home/username/docker/DUMB/data:/data
      - /home/username/docker/DUMB/mnt/debrid:/mnt/debrid
    environment:
      - TZ=
      - PUID=
      - PGID=
    ports:
      - "3005:3005"
    devices:
      - /dev/fuse:/dev/fuse:rwm
      - /dev/dri:/dev/dri
    cap_add:
      - SYS_ADMIN
    security_opt:
      - apparmor:unconfined

🌐 Environment Variables

The following table lists the required environment variables used by the container. The environment variables are set via the -e parameter or via the docker-compose file within the environment: section or with a .env file saved to the config directory. Value of this parameter is listed as <VARIABLE_NAME>=<Value>

Variables required by DUMB:

See the .env.example

🌐 Default Ports Used

[!NOTE] The below examples are default and may be configurable with the use of additional environment variables.

The following table describes the ports used by the container. The mappings are set via the -p parameter or via the docker-compose file within the ports: section. Each mapping is specified with the following format: <HOST_PORT>:<CONTAINER_PORT>[:PROTOCOL].

cloudflared does not expose a local web UI port. It opens an outbound Cloudflare Tunnel connection and forwards public hostname traffic to DUMB Traefik.

📂 Data Volumes

The following table describes the data volumes used by the container. The mappings are set via the -v parameter or via the docker-compose file within the volumes: section. Each mapping is specified with the following format: <HOST_DIR>:<CONTAINER_DIR>[:PERMISSIONS].

📝 TODO

See the DUMB roadmap for a list of planned features and enhancements.

🚀 Deployment

DUMB allows for the simultaneous or individual deployment of any of the services

For additional details on deployment, see the DUMB Docs

🌍 Community

• For questions related to DUMB, see the GitHub discussions
• or create a new issue if you find a bug or have an idea for an improvement.
• or join the DUMB discord server