Skip to content

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

Open
jimnoneill wants to merge 1 commit into
pulsejet:masterfrom
jimnoneill:docs-remote-gpu-community-guide
Open

docs: link community guide for running go-vod on a separate GPU host#1653
jimnoneill wants to merge 1 commit into
pulsejet:masterfrom
jimnoneill:docs-remote-gpu-community-guide

Conversation

@jimnoneill
Copy link
Copy Markdown

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 occ calls 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

  • Rendered the admonition in mkdocs locally to confirm it matches the style of the surrounding tips
  • Verified link target resolves

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant