From 524cbc4ff519ba45ad39ff9a91fdb0aa5f40840a Mon Sep 17 00:00:00 2001 From: Jamey O'Neill Date: Thu, 16 Apr 2026 13:16:47 -0700 Subject: [PATCH] docs: link community guide for running go-vod on a separate GPU host over NFS --- docs/hw-transcoding.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/hw-transcoding.md b/docs/hw-transcoding.md index 67e878bc1..339c34fd1 100644 --- a/docs/hw-transcoding.md +++ b/docs/hw-transcoding.md @@ -111,6 +111,10 @@ services: group_add: [109] ``` +!!! tip "GPU on a separate machine" + + If your Nextcloud host does not have a GPU, you can also run go-vod on a different machine entirely and mount the Nextcloud data over NFS. A community-maintained setup guide and deploy script for this configuration (NVIDIA GPU with NVENC, NFS mount, external transcoder) is available at [jimnoneill/nextcloud-memories-gpu](https://github.com/jimnoneill/nextcloud-memories-gpu). + ## Internal Transcoder Memories ships with an internal transcoder binary that you can directly use. In this case, you must install the drivers and ffmpeg on the same host as Nextcloud, and Memories will automatically handle starting and communicating with go-vod. This is also the default setup when you enable transcoding without hardware acceleration.