Difference between revisions of "Mediaserver - Jellyfin"

From Da Nerd Mage Wiki
Jump to navigation Jump to search
Line 23: Line 23:


Current Live Server:
Current Live Server:
* Debian 11 Minimal
* Debian 11 [[Mini Debian{{!}}Minimal]]
** CPU: 2 sockets, 4 cores each
** CPU: 2 sockets, 4 cores each
** RAM: 16GB
** RAM: 16GB

Revision as of 16:16, 27 April 2023

W...I...P...

Proven on:
Logo Debian.png
11 (bullseye)


Requirements

Jellyfin is not particularly resource hungry in general.

I've found that the most common "slowdowns" are caused be library scanning. If you add a whole lot of media to the libraries at once, (like multiple TB...) it'll bog down for a long time.

Current testbed:

  • Debian LXC
    • CPU: 4 cores
    • RAM: 2048MB
    • DISK: 64GB

I'm actually running it live on a Debian VM, but the testbed is being used to write this page...

Current Live Server:

  • Debian 11 Minimal
    • CPU: 2 sockets, 4 cores each
    • RAM: 16GB
    • DISK: 64GB

Playing back a 1080p HEVC video seems to use ALL of the CPU. No difficulty with the playback, but it grabs the CPU hard & uses it.

Installation

  • sudo apt install curl gnupg
  • curl https://repo.jellyfin.org/install-debuntu.sh | sudo bash

Pretty hard... eh?

Storage

Personally, I like to use NFS for my data storage needs.

You could simply try to give the media server enough local storage for ALL of your media, but, how much storage will you eventually need? (Hint: More than you think...)

Initial Configuration

  1. Browse to http://MEDIASERVER:8096
    • (Replace MEDIASERVER with the IP or FQDN of your server...)
  2. Follow the prompts
    • (Admin user will be able to manage the server through the WEB UI)

Setting Up Your Media libraries

Some Reference Materials

Some Useful Links

Oddities & Issues