From 2cc31aa56764df9415452a4b540859a73431b456 Mon Sep 17 00:00:00 2001 From: Varun Patil Date: Thu, 16 Nov 2023 15:55:35 -0800 Subject: [PATCH] docs: document AIO community container Signed-off-by: Varun Patil --- docs/hw-transcoding.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/hw-transcoding.md b/docs/hw-transcoding.md index 441bb49d..f020ccbf 100644 --- a/docs/hw-transcoding.md +++ b/docs/hw-transcoding.md @@ -74,10 +74,11 @@ NVIDIA GPUs support hardware transcoding using NVENC. Your external transcoder should now be functional. You can check the transcoding logs by running `docker compose logs -f go-vod`. -!!! info "Usage with Nextcloud AIO" +!!! tip "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`. - See the instructions [here](https://github.com/nextcloud/all-in-one#how-to-enable-hardware-transcoding-for-nextcloud). + With 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 as in its Nextcloud container into the go-vod container. Usually this would be `nextcloud_aio_nextcloud_data:/mnt/ncdata:ro` or `$NEXTCLOUD_DATADIR:/mnt/ncdata:ro`. + + If you are not using NVENC, you can also skip these steps and use the **memories community container** instead. Relevant documentation can be found [here](https://github.com/nextcloud/all-in-one/tree/main/community-containers/memories), and general directions on using community containers [here](https://github.com/nextcloud/all-in-one/tree/main/community-containers). AIO v7.7.0 or higher is required. !!! info "Usage without Docker Compose"