Memories and Recognize work fine with the base Nextcloud docker image. My host has a GPU so I use go-vod to leverage hardware transcoding. The base NC docker image can't access Nvidia cards (probably other GPUs as well). I could script in a way to do this but would need to run it after each update. Recognize runs fine on my CPU so I haven't explored this yet.
I have an OpenMediaVault VM with a 10tb volume in the network that runs the S3 plugin (Minio-based) which is connected through Nextcloud's external storage feature (I want to migrate to Garage soon). I believe notify_push helps desktop clients cut down on the chatter when querying the external storage folder. Limiting the users that can access this also helps.
I was having issues getting the notify_push app [1] to work in the container with my reverse-proxy. I found some similar setups that did this [2], so I added another nextcloud container to the docker-compose yaml like so:
notify_push:
image: nextcloud
restart: unless-stopped
ports:
- 7867:7867
depends_on:
- app
environment:
- PORT=7867
- NEXTCLOUD_URL=http://<local ip address of docker server>:8081
entrypoint: /var/www/html/custom_apps/notify_push/bin/x86_64/notify_push /var/www/html/config/config.php
volumes:
- /path/to/nextcloud/customapps:/var/www/html/custom_apps
- /path/to/nextcloud/config:/var/www/html/config
[1] - https://apps.nextcloud.com/apps/notify_push[2] - https://help.nextcloud.com/t/docker-caddy-fpm-notify-push-ca...
Do you know if there's any way to `Recognize this image now` via the GUI? Whilst twiddling my thumbs for a few decades of photos to import, I go through what's there and occasionally a family member will point and tell me who a pic is of, but can't seem to immediately prioritise or `Recognize` the specific pic so I can add a name to the face.
Who's your host?