FinTV

FinTV creates virtual 24/7 TV channels from a Jellyfin media library and broadcasts them as HLS (HTTP Live Streaming) feeds.

  • Media Servers
  • Tools & Utilities
FinTV creates virtual 24/7 TV channels from a Jellyfin media library and broadcasts them as HLS (HTTP Live Streaming) feeds. The same container hosts the repository for the FinTV Jellyfin plugin, so the plugin can be installed and managed directly from the Jellyfin dashboard. It supports CPU encoding via libx264 with optional NVIDIA NVENC hardware acceleration, configurable media path mappings, and API-key authentication, making it a good fit for homelab users who want their movies, shows, and music to stream continuously to TVs, tablets, and other devices.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

42/100 Fair

Maintained
72last commit 4 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
0
Open issues
0
Last commit
2026-11-16
License
MIT
Activity
rising

Checked 4 days ago - source: GitHub (SolidProgramming/UnraidTemplates)

Resources & Compatibility

Requirements not published yet.

Checked 4 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Pre-create the config directory Before first start, run in the Unraid terminal: mkdir -p /mnt/user/appdata/fintv && chown 99:100 /mnt/user/appdata/fintv. The container runs as UID:GID 99:100; if Docker creates the directory as root instead, the service stops with 'Applying database migrations failed' in the log. source
  • API key, media mount, and path mapping Set an API key of at least 32 characters (for example generated with 'openssl rand -hex 32') and mount the media share under /media. Then configure the path mapping pairs so the container sees the same files as Jellyfin (From = path in Jellyfin, To = path in the container). source
  • Health check and Jellyfin plugin Start the container and confirm the health endpoint responds at http://[IP]:8098/health. Then in Jellyfin go to Dashboard, Plugins, Repositories, add the FinTV plugin repository (served by the FinTV container itself), and install the FinTV plugin from the plugin list. source
  • Persistent Storage Persistent configuration and database storage are maintained by the container. source

Fetched yesterday - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why does FinTV fail on first start with "Applying database migrations failed"?

The container runs as UID 99 / GID 100 and expects the appdata directory to already exist with that ownership. Pre-create it in the Unraid terminal with mkdir -p /mnt/user/appdata/fintv and chown 99:100 /mnt/user/appdata/fintv before the first start; otherwise Docker creates the directory as root and the service cannot write the database.

How do I configure media path mappings so FinTV finds the same files Jellyfin uses?

Mount the media share at /media inside the container, then set the path mapping "From" to the path as it appears in Jellyfin and "To" to the corresponding path inside the container.

Can FinTV use hardware-accelerated encoding?

By default it encodes on the CPU with libx264, but optional NVIDIA NVENC acceleration is available if you have an NVIDIA GPU and the Unraid Nvidia Driver plugin installed.

What are the requirements for the FinTV API key?

The key must be at least 32 characters. A practical way to generate one is to run openssl rand -hex 32 in the terminal and use the output.

Answers sourced from github.com

Community

No community discussions collected yet.