From 775d2009c4e69d0995a8400b91bb796cc48d5a0d Mon Sep 17 00:00:00 2001 From: "Joshua M. Boniface" Date: Tue, 30 Jun 2020 12:55:51 -0400 Subject: [PATCH] Mention unrecommended full-network export ACLs --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ccaad73..eae3a9e 100644 --- a/README.md +++ b/README.md @@ -38,7 +38,7 @@ This example setup is the one I use for `rffmpeg`, involving a media server (`jf 1. Install the NFS kernel server: `sudo apt -y install nfs-kernel-server` -1. Export your Jellyfin data path found in step 1 with NFS; you will need to know the local IP address of the transcode server(s) (e.g. `10.0.0.100`) to lock this down; alternatively, use your entire local network range (e.g. `10.0.0.0/24`): `echo '/var/lib/jellyfin 10.0.0.100/32(rw,sync,no_subtree_check)' | sudo tee -a /etc/exports && sudo systemctl restart nfs-kernel-server` +1. Export your Jellyfin data path found in step 1 with NFS; you will need to know the local IP address of the transcode server(s) (e.g. `10.0.0.100`) to lock this down; alternatively, use your entire local network range (e.g. `10.0.0.0/24`), though this is not recommended for security reasons: `echo '/var/lib/jellyfin 10.0.0.100/32(rw,sync,no_subtree_check)' | sudo tee -a /etc/exports && sudo systemctl restart nfs-kernel-server` 1. On the transcode server, install any required tools or programs to make use of hardware transcoding; this is optional if you only use software (i.e. CPU) transcoding.