From 65e4bfbccc40dc46ffde9156c46683c96a04c3bc Mon Sep 17 00:00:00 2001 From: Joshua Boniface Date: Sat, 19 Oct 2019 19:01:49 -0400 Subject: [PATCH] Mention UID compatibility --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f73ec8c..54cb131 100644 --- a/README.md +++ b/README.md @@ -28,7 +28,7 @@ This example setup is the one I use for `rffmpeg`, involving a Jellyfin server ( 1. Create a temporary transcoding directory somewhere on the system. Ideally, this should be fast scratch storage with no persistence required. In my case I use a pair of RAID-0 SSDs, though you could use a ramdisk if you have sufficient RAM. For my purposes, I put this directory at `/var/transcode` and mount my SSD RAID there. - 1. Create a user to accept SSH connections in and run the FFmpeg commands. I use a user called `jellyfin` with a home directory of `/var/lib/jellyfin`, identical to the user that is created by the Jellyfin server itself - this is important for the directory layout to work. + 1. Create a user to accept SSH connections in and run the FFmpeg commands. I use a user called `jellyfin` with a home directory of `/var/lib/jellyfin`, identical to the user that is created by the Jellyfin server itself - this is important for the directory layout to work. For maximum compatibility, ensure this user has the exact same Unix UID as the Jellyfin user on your Jellyfin host. 1. Ensure the temporary transcoding directory is owned by the new user.