Interest in an optional media-library web UI for docker-transmission-openvpn and Arr-stack users?

[Elanoran]

Hi!

I’ve been experimenting with an optional modern web UI layer for docker-transmission-openvpn, and wanted to ask if this could be of interest in some form.

The goal is not to replace Transmission itself or change the core VPN/container behavior. It is more of a media-library aware UI for people using Transmission together with Radarr/Sonarr/Lidarr.

The prototype tries to solve this by adding:

• A media-library style view with clean titles instead of raw release names.
• Posters and metadata from Radarr/Sonarr/Lidarr, so torrents are easier to recognize at a glance.
• A small optional helper container that writes a local metadata cache, keeping API keys/config out of the browser.
• A queue controller that can detect stale/low-progress downloads and help keep limited download slots moving.
• Preferences/settings backed by real Transmission RPC instead of static UI-only controls.
• A demo mode with fictional torrents/posters, so screenshots and docs can be shared without exposing real torrent names.
• An optional TRANSMISSION_WEB_UI=library mode while keeping the existing bundled UIs available.

I have this working locally, but my preference would be to avoid creating another long-lived fork if this is something that could fit upstream. I wanted to check interest before polishing it further or pushing a public branch.

Screenshots

Demo data only, no real torrents shown.

Library grid view
Torrents shown as recognizable media items with posters, clean titles, Arr source badges, progress, speed, queue state, and media-type filters.

List view
Dense management view for active downloads, seeding items, queued torrents, and items needing attention. Metadata, progress, peers, speeds, and quick actions stay visible.

Speed limits and queue controls
Transmission-backed speed controls with turtle mode, caps, quiet hours, and visible queue controller status.

Add torrent dialog
Drag-and-drop .torrent support, magnet/torrent URL input, priority selection, and start-immediately control.

[ilike2burnthing]

Not a dev here, but familiar enough with their ethos of keeping things as simple as possible, which wouldn't fit with what you've described. Nothing stops you using the work here in your own project, in line with its license - https://github.com/haugene/docker-transmission-openvpn/blob/master/LICENSE