Skip to content

docs: link community guide for running go-vod on a separate GPU host #1653

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jimnoneill wants to merge 1 commit into
base: master
Choose a base branch
from
+4 −0
Open

docs: link community guide for running go-vod on a separate GPU host #1653

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/hw-transcoding.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down