RPJosh
/
memories
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: minor updates to hw 

Signed-off-by: Varun Patil <radialapps@gmail.com>
pull/888/head
Varun Patil 2023-10-20 21:46:04 -07:00
parent 7a7cf46a72
commit 4a89dd16c7
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/hw-transcoding.md
View File

@ -32,7 +32,7 @@ NVIDIA GPUs support hardware transcoding using NVENC.
This setup utilizes a separate docker container that contains the hardware drivers and ffmpeg. This setup utilizes a separate docker container that contains the hardware drivers and ffmpeg.
If you cannot do this, other installation methods are also possible (see below). If you cannot do this, other installation methods are also possible (see below).
!!! warning "Memories v6+" !!! warning "Memories v6+ required"
This method is only supported in Memories v6 and newer. For older versions, see [below](#external-transcoder-v5). This method is only supported in Memories v6 and newer. For older versions, see [below](#external-transcoder-v5).
@ -53,24 +53,24 @@ NVIDIA GPUs support hardware transcoding using NVENC.
depends_on: depends_on:
- server - server
environment: environment:
- NEXTCLOUD_HOST=https://your-nextcloud-host - NEXTCLOUD_HOST=https://your-nextcloud-url
# - NEXTCLOUD_ALLOW_INSECURE=1 # (uncomment if using http or self-signed certs) # - NEXTCLOUD_ALLOW_INSECURE=1 # (self-signed certs or no HTTPS)
- NVIDIA_VISIBLE_DEVICES=all - NVIDIA_VISIBLE_DEVICES=all
devices: devices:
- /dev/dri:/dev/dri # VA-API device (omit for NVENC) - /dev/dri:/dev/dri # VA-API (omit for NVENC)
volumes: volumes:
- ncdata:/var/www/html:ro - ncdata:/var/www/html:ro
# runtime: nvidia # (uncomment for NVENC) # runtime: nvidia # (NVENC)
``` ```
!!! note "Devices and volumes" !!! info "Device and volume bindings"
In this example, the VA-API devices in `/dev/dri` are passed to the container, along with the Nextcloud data directory (as readonly). All volumes must be mounted at the same location as the Nextcloud container. In this example, the VA-API devices in `/dev/dri` are passed to the container, along with the Nextcloud data directory (as readonly). All volumes must be mounted at the same location as the Nextcloud container.
!!! tip "NVENC" !!! question "What to set in `NEXTCLOUD_HOST`?"
If you want to use NVENC instead of VA-API, uncomment the `runtime` line and remove the `devices` section above. You will need to install the [NVIDIA Container Toolkit](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html) on your host. The `NEXTCLOUD_HOST` environment variable must be set to the URL of your Nextcloud instance. If you are using a reverse proxy, you must set this to the URL of the reverse proxy. If you are using a self-signed certificate or http, you must also set `NEXTCLOUD_ALLOW_INSECURE=1`. This URL is used to download the transcoder binary and to connect to the Nextcloud instance.
!!! tip "Nextcloud host" !!! tip "Setup for NVENC"
The `NEXTCLOUD_HOST` environment variable must be set to the URL of your Nextcloud instance. If you are using a reverse proxy, you must set this to the URL of the reverse proxy. If you are using a self-signed certificate or http, you must also set `NEXTCLOUD_ALLOW_INSECURE=1`. Note that you may directly use the name of the Nextcloud container if you are using Docker Compose, but you will need to add the domain to `trusted_domains` in `config.php`. If you want to use NVENC instead of VA-API, uncomment the `runtime` line and remove the `devices` section above. You will need to install the [NVIDIA Container Toolkit](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html) on your host.
1. You can now configure the go-vod connect address in the Memories admin panel to point to the external container. go-vod uses port `47788` by default, so in our example the **connection address** would be set to **`go-vod:47788`**. 1. You can now configure the go-vod connect address in the Memories admin panel to point to the external container. go-vod uses port `47788` by default, so in our example the **connection address** would be set to **`go-vod:47788`**.
@ -80,7 +80,7 @@ Your external transcoder should now be functional. You can check the transcoding
!!! info "Usage with Nextcloud AIO" !!! info "Usage with Nextcloud AIO"
With Nextcloud AIO, you will need to put the container into the `nextcloud-aio` network. Also the datadir of AIO needs to be mounted at the same place like in its Netxcloud container into the go-vod container. Usually this would be `nextcloud_aio_nextcloud_data:/mnt/ncdata:ro` or `$NEXTCLOUD_DATADIR:/mnt/ncdata:ro`. With Nextcloud AIO, you will need to put the container into the `nextcloud-aio` network. Also the `datadir` of AIO needs to be mounted at the same place like in its Netxcloud container into the go-vod container. Usually this would be `nextcloud_aio_nextcloud_data:/mnt/ncdata:ro` or `$NEXTCLOUD_DATADIR:/mnt/ncdata:ro`.
See the instructions [here](https://github.com/nextcloud/all-in-one#how-to-enable-hardware-transcoding-for-nextcloud). See the instructions [here](https://github.com/nextcloud/all-in-one#how-to-enable-hardware-transcoding-for-nextcloud).
!!! info "Usage without Docker Compose" !!! info "Usage without Docker Compose"