technology

Install jellyfin, both fbackend and frontend

# pacman -S jellyfin-server jellyfin-web

Start jellyfin

# systemctl start jellyfin

Usually you'd edit some config file in /etc first but jellyfin is 'user friendly' so you log in at http://localhost:8096/ and configure from there.

Set the service to automatically start at boot

# systemctl enable jellyfin

View logs of the jellyfin service with (use -fu to watch them). Very useful for debugging issues.

# journalctl -u jellyfin

The most common issue is that the jellyfin service will run as its own user which might not have permissions to your archive of media.

Containers

If you're installing with containers the easiest to set up is with docker-compose. Basically you write a yaml file that defines all the different services, networks, and most importantly: where the containers can access your host system. I'm not going to explain more because there's excellent documentation and probably tutorials for exactly your case.

Quadlets are like a docker-compose file but split into different files, use podman instead of docker, and are managed by systemd. You write each container, volume, and network as its own file in /etc/containers/, run # systemctl daemon-reload and that magically generates .service files and then you can start and manage them like they were a native application.

Caveat, I've only recently dipped my toes into quadlets but I'm already enamored with them. My only gripe is if you get the quadlet files systax wrong you will see no warnings unless you check journalctl. Docker-compose is definitely easier to set up and I do recommend learning with that first. IMO its easier to learn docker-compose before docker.

Also

Plex