Your personal media companion, built with Phoenix LiveView

A modern, self-hosted media management platform for tracking, organizing, and monitoring your media library.

• 📺 Smart Media Library – Track TV shows, movies, and episodes with rich metadata from TMDB/TVDB
• 🔍 Media Discovery – Search and add content with automatic metadata matching and disambiguation
• 📁 Library Scanner – Automatic scanning and import of existing media files
• 🎬 Detailed Media Pages – View comprehensive information including cast, crew, seasons, and episodes
• 📊 Quality Profiles – Customizable quality preferences for automated downloads

• ⬇️ Download Client Integration – Seamless connectivity with torrent clients (qBittorrent, Transmission) and Usenet clients (SABnzbd, NZBGet)
• 🔎 Indexer Support – Integrated search via Prowlarr and Jackett for finding releases
• 🤖 Automatic Search & Download – Background jobs to automatically find and download monitored content
• 🎯 Smart Release Ranking – Pluggable scoring system to select the best matching releases
• 📥 Manual Search – Browse and select specific releases from the UI
• 📋 Download Queue – Real-time monitoring of active downloads with progress tracking
• 🌐 Usenet Support – Native support for Usenet downloads with SABnzbd and NZBGet clients

• 🔔 Release Calendar – Track upcoming and past releases with timeline view
• 👁️ Episode Monitoring – Monitor individual episodes, seasons, or entire series
• 📊 Missing Episodes – Identify gaps in your library
• ⏱️ Background Jobs – Automated scanning, searching, and importing with Oban

• 👥 Role-Based Access – Admin and guest user roles with appropriate permissions
• 🎫 Guest Request System – Guests can browse media and submit requests for new content
• ✅ Request Approval Workflow – Admins review and approve/reject guest requests with notes
• 📊 Request Tracking – Users can monitor the status of their media requests
• 🔐 Multi-Auth Support – Local authentication and OIDC/OpenID Connect integration
• 🚀 Auto-Promotion – First OIDC user automatically promoted to admin role

• ⚙️ Admin Dashboard – System status, configuration management, and health monitoring
• 🔧 Flexible Configuration – Environment variables, YAML files, or database settings with clear precedence
• 🎨 Modern UI – Built with Phoenix LiveView, Tailwind CSS, and DaisyUI
• 🐳 Docker Ready – Pre-built images for amd64 and arm64 platforms

Dashboard	Movies
TV Shows	Calendar View
Search

Multi-platform images are available for the following architectures:

The multi-arch image ghcr.io/getmydia/mydia:latest will automatically pull the correct image for your architecture.

1. Generate required secrets:

# Generate SECRET_KEY_BASE
openssl rand -base64 48

# Generate GUARDIAN_SECRET_KEY
openssl rand -base64 48

2. Set up your container using Docker Compose (recommended) or Docker CLI
3. Access the web interface at http://your-server:4000
4. On first startup, a default admin user is automatically created:
   • Check the container logs for the generated password
   • Default username: admin (configurable via ADMIN_USERNAME)
   • Or set ADMIN_PASSWORD_HASH to use a pre-hashed password
5. Configure download clients and indexers in the Admin section

Here are some example snippets to help you get started creating a container.

---
services:
  mydia:
    image: ghcr.io/getmydia/mydia:latest
    container_name: mydia
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/New_York
      - SECRET_KEY_BASE=your-secret-key-base-here  # Required: generate with openssl rand -base64 48
      - GUARDIAN_SECRET_KEY=your-guardian-secret-key-here  # Required: generate with openssl rand -base64 48
      - PHX_HOST=localhost  # Change to your domain
      - PORT=4000
      - MOVIES_PATH=/media/library/movies
      - TV_PATH=/media/library/tv
    volumes:
      - /path/to/mydia/config:/config
      - /path/to/your/media:/media  # Single mount enables hardlinks between downloads and libraries
    ports:
      - 4000:4000
    restart: unless-stopped

Note: This example uses a single /media mount to enable hardlink support. Organize your host directory with subdirectories like /path/to/your/media/downloads, /path/to/your/media/library/movies, and /path/to/your/media/library/tv. Configure your download client to save to /media/downloads.

docker run -d \
  --name=mydia \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=America/New_York \
  -e SECRET_KEY_BASE=your-secret-key-base-here \
  -e GUARDIAN_SECRET_KEY=your-guardian-secret-key-here \
  -e PHX_HOST=localhost \
  -e PORT=4000 \
  -e MOVIES_PATH=/media/library/movies \
  -e TV_PATH=/media/library/tv \
  -p 4000:4000 \
  -v /path/to/mydia/config:/config \
  -v /path/to/your/media:/media \
  --restart unless-stopped \
  ghcr.io/getmydia/mydia:latest

Note: This example uses a single /media mount to enable hardlink support. Configure your download client to save to /media/downloads.

Container images are configured using parameters passed at runtime. These parameters are separated by a colon and indicate external:internal respectively.

See the Environment Variables Reference section below for complete configuration options including download clients, indexers, and authentication.

💡 Hardlink Support for Efficient Storage

For optimal storage efficiency, mydia uses hardlinks by default when importing media. Hardlinks allow the same file to appear in both your download folder and library folder without consuming additional disk space.

To enable hardlinks, ensure your downloads and library directories are on the same filesystem by using a single parent volume mount:

volumes:
  - /path/to/mydia/config:/config
  - /path/to/your/media:/media  # Single mount for downloads AND libraries

Then organize your host directory structure like:

/path/to/your/media/
  ├── downloads/          # Download client output
  ├── library/
  │   ├── movies/         # Movies library
  │   └── tv/             # TV library

And configure environment variables:

environment:
  - MOVIES_PATH=/media/library/movies
  - TV_PATH=/media/library/tv

Configure your download client (qBittorrent, Transmission, etc.) to save files to /media/downloads.

Benefits:

• Instant file operations (no data copying)
• Zero duplicate storage space
• Files remain seeding in your download client while available in your library

Note: If your downloads and libraries must be on different filesystems, mydia will automatically fall back to copying files. This works fine but uses more storage space and takes longer.

When using volumes (-v flags), permissions issues can arise between the host and container. To avoid this, specify the user PUID and group PGID to ensure files created by the container are owned by your user.

Finding your IDs:

id your_user

Example output: uid=1000(your_user) gid=1000(your_user)

Use these values for PUID and PGID in your container configuration.

Conflict Handling:

The entrypoint script automatically handles conflicts when the specified PUID/PGID is already in use by another user or group in the container. For example, GID 100 is typically used by the "users" group in Alpine Linux. The container will automatically resolve these conflicts by removing the conflicting user/group and applying your specified IDs.

Common scenarios:

• Using PGID=100 (conflicts with "users" group) - automatically handled ✓
• Using PUID=99 (conflicts with "nobody" user on some systems) - automatically handled ✓
• Any custom UID/GID that matches your host system - automatically handled ✓

The container logs will show which conflicts were resolved during startup.

docker compose pull
docker compose up -d

docker stop mydia
docker rm mydia
docker pull ghcr.io/getmydia/mydia:latest
# Run your docker run command again

Note: Migrations run automatically on startup. Your data in /config is preserved across updates.

See DEPLOYMENT.md for advanced deployment topics.

User Roles:

• Admin: Full access to all features including media management, downloads, configuration, and request approval
• Guest: Can browse media library and submit requests for new content that require admin approval

OIDC Auto-Promotion: The first user to log in via OIDC is automatically promoted to admin role. Subsequent OIDC users are assigned the guest role by default.

Admin User Creation:

On first startup, if no admin user exists, Mydia automatically creates one:

• Random Password (default): A secure random password is generated and displayed in the container logs
• Pre-set Password: Use ADMIN_PASSWORD_HASH with a bcrypt hash for production deployments

Generate a bcrypt hash:

# Using Elixir/Mix (if available)
mix run -e "IO.puts Bcrypt.hash_pwd_salt(\"your_secure_password\")"

# Using Python
python3 -c "import bcrypt; print(bcrypt.hashpw(b'your_secure_password', bcrypt.gensalt()).decode())"

Configure multiple download clients using numbered environment variables (<N> = 1, 2, 3, etc.):

Supported Download Clients:

• Torrent Clients: qBittorrent, Transmission
• Usenet Clients: SABnzbd, NZBGet

Example configurations:

# qBittorrent
DOWNLOAD_CLIENT_1_NAME=qBittorrent
DOWNLOAD_CLIENT_1_TYPE=qbittorrent
DOWNLOAD_CLIENT_1_HOST=qbittorrent
DOWNLOAD_CLIENT_1_PORT=8080
DOWNLOAD_CLIENT_1_USERNAME=admin
DOWNLOAD_CLIENT_1_PASSWORD=adminpass

# Transmission
DOWNLOAD_CLIENT_2_NAME=Transmission
DOWNLOAD_CLIENT_2_TYPE=transmission
DOWNLOAD_CLIENT_2_HOST=transmission
DOWNLOAD_CLIENT_2_PORT=9091
DOWNLOAD_CLIENT_2_USERNAME=admin
DOWNLOAD_CLIENT_2_PASSWORD=adminpass

# SABnzbd (Usenet)
DOWNLOAD_CLIENT_3_NAME=SABnzbd
DOWNLOAD_CLIENT_3_TYPE=sabnzbd
DOWNLOAD_CLIENT_3_HOST=sabnzbd
DOWNLOAD_CLIENT_3_PORT=8080
DOWNLOAD_CLIENT_3_API_KEY=your-sabnzbd-api-key

# NZBGet (Usenet)
DOWNLOAD_CLIENT_4_NAME=NZBGet
DOWNLOAD_CLIENT_4_TYPE=nzbget
DOWNLOAD_CLIENT_4_HOST=nzbget
DOWNLOAD_CLIENT_4_PORT=6789
DOWNLOAD_CLIENT_4_USERNAME=nzbget
DOWNLOAD_CLIENT_4_PASSWORD=tegbzn6789

Configure multiple indexers using numbered environment variables (<N> = 1, 2, 3, etc.):

Example for Prowlarr:

INDEXER_1_NAME=Prowlarr
INDEXER_1_TYPE=prowlarr
INDEXER_1_BASE_URL=http://prowlarr:9696
INDEXER_1_API_KEY=your-prowlarr-api-key-here

Example for Jackett:

INDEXER_2_NAME=Jackett
INDEXER_2_TYPE=jackett
INDEXER_2_BASE_URL=http://jackett:9117
INDEXER_2_API_KEY=your-jackett-api-key-here

Configuration is loaded in this order (highest to lowest priority):

1. Environment Variables - Override everything
2. Database Settings - Configured via Admin UI
3. YAML File - From config/config.yml
4. Schema Defaults - Built-in defaults

With Docker (Recommended):

# Start everything
./dev up -d

# Run migrations
./dev mix ecto.migrate

# View at http://localhost:4000
# Check logs for the auto-generated admin password:
./dev logs | grep "DEFAULT ADMIN USER CREATED" -A 10

See all commands with ./dev

Without Docker:

mix setup
mix phx.server

Visit localhost:4000

All pull requests and commits to the main branch automatically run:

• ✓ Code compilation with warnings as errors
• ✓ Code formatting checks
• ✓ Static analysis with Credo
• ✓ Full test suite
• ✓ Docker build verification

Run these checks locally before committing:

mix precommit

Create compose.override.yml to add services like Transmission, Prowlarr, Jackett, or custom configurations:

cp compose.override.yml.example compose.override.yml
# Edit and uncomment services you need
./dev up -d

Capture automated screenshots for documentation:

./take-screenshots

See assets/SCREENSHOTS.md for configuration options.

• Phoenix 1.8 + LiveView
• Ecto + SQLite
• Oban (background jobs)
• Tailwind CSS + DaisyUI
• Req (HTTP client)

Built with Elixir & Phoenix