docs: link community guide for running go-vod on a separate GPU host#1653
Open
jimnoneill wants to merge 1 commit into
Open
docs: link community guide for running go-vod on a separate GPU host#1653jimnoneill wants to merge 1 commit into
jimnoneill wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Small docs addition under the External Transcoder section of
docs/hw-transcoding.md.The existing examples in that section assume go-vod runs on the same host as Nextcloud (shared docker network, shared data volumes). I put together a setup guide for the other common case, where the Nextcloud storage server does not have a GPU and the transcoder runs on a separate machine with the Nextcloud data mounted over NFS. Useful for folks running Nextcloud on a NAS or low-power box who have a homelab node or old gaming PC with an NVIDIA card sitting around.
The repo has a deploy script that handles NFS exports on the storage side, the go-vod container with the NVIDIA Container Toolkit on the GPU side, and the
occcalls to configure Memories. It also documents the GOP size workaround up front, which cost me an evening the first time.Repo: https://github.com/jimnoneill/nextcloud-memories-gpu
Happy to adjust the wording or the placement if you would rather link from somewhere else, or skip this entirely if you do not want external setup guides referenced from the docs. No hard feelings either way.
Thanks for Memories. It is the piece that made self hosting photos actually pleasant.
Test plan