From 94cebebfb55986188b26137e3bf4e7b722a4bf30 Mon Sep 17 00:00:00 2001 From: Joshua Boniface Date: Sat, 19 Oct 2019 18:20:36 -0400 Subject: [PATCH] Mention SSH key acceptance and testing command --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 1d0cb85..abd705f 100644 --- a/README.md +++ b/README.md @@ -40,7 +40,9 @@ This example setup is the one I use for `rffmpeg`, involving a Jellyfin server ( 1. On your Jellyfin server, create a new SSH private keypair owned by the Jellyfin service user. -1. Install the public key of the new SSH private keypair under the remote user on the transcode server. Verify that SSH is successful from the Jellyfin server to the transcode server as the selected user. +1. Install the public key of the new SSH private keypair under the remote user on the transcode server. + +1. Verify that SSH is successful from the Jellyfin server (as the Jellyfin user) to the transcode server as expected. Running `sudo -u rffmpeg.py` once with no arguments will accomplish this test. This also ensures that the SSH host key of the remote server is saved before Jellyfin attempts to run the command. 1. Install the NFS client, and mount the temporary transcoding directory from the remote server to your `transcoding-temp` directory as set in Jellyfin.