I have a VPS, but no root access so I can’t use apt, or even read a lot of the system files. I would like to get jellyfin (or any media server, really) running on it. Jellyfin has a portable installation option, so I followed the instructions in the docs to install it from the .tar.gz.
But it says I have to install ffmpeg-jellyfin, and I can’t find a portable installation of that. My VPS already has ffmpeg installed on it. Will jellyfin work if I just point it to that instead? Or, how can I go about installing ffmpeg-jellyfin without root access?
I run it in Podman rootless
Jellfin can be configured to use specific installed versions of ffmpeg.
If you do need the jellyfin-ffmpeg (which is needed in specific installs) then you can download releases from github or build it yourself. They do have portable releases.
You do not necessarily need root access to use software on Linux unless you’re trying to install it to be available to all users. Users can often install their own software either binaries or compile themselves (unless the system has been locked down). They could sit within your /home/username/bin directory instead of the system level folders like /usr/bin normally used for non-root executable. Your home bin folder is only accessible and so runable by you, and is viable if you do not have access or permission to install into /usr/bin.
You can configure jellyfin to run within your home bin folder or run other software within that folder.
You can get the jellyfin ffmpeg source and releases including portables from their git: https://github.com/jellyfin/jellyfin-ffmpeg
Why do you not have root? This isn’t a case of unauthorized use is it? If you paying for a VPS you should have root.
Side note: I personally would run Jellyfin on a Intel minipc for hardware acceleration.
Why not use a docker image?
That requires root
I thought there is a rootless docker?
You’re right, that might work
podman then
I run it in podman in user context, root is not required
If you don’t have root is it really a VPS?
Anyway, unpack the binaries to
~/local/usr/binand add that to your PATH.~/.local/binis more typicalIt doesn’t matter. Put it in ~/foo/bar/Baz for all the shell cares.
Of course. That path is just likely already there, and the prefix works for every thing else like desktop files, icons, services, etc. In this context whatever but its a reasonable default choice.
