This is a support thread for the VideoWare Docker Container for unRAID. Project homepage: https://makeware.io/projects/video-ware Source / Issues: https://github.com/make-ware/video-ware Container Registry: ghcr.io/make-ware/video-ware:latest (linux/amd64, linux/arm64) License: AGPL-3.0 You can find this container in Community Applications. Storage VideoWare keeps everything in /data – library + DB. On unRAID that's typically /mnt/user/appdata/video-ware. It writes to local disk or any S3-compatible store. I run mine against garageHQ for S3 – any S3 endpoint works, put the bucket / keys in the template env. If you're just starting, local disk is fine and will be more stable! You can move to S3 later. S3 will reduce the local footprint but disk space will be consumed during transcoding and render operations. CLI If you want to create videos using scripts, or even enable coding agents to interact with your video footage you can download and install the CLI. It provides parity with web based UI, and will allow you to automate much of the video editing workflow. Labeling By default there is no data labeling, it's just a web based video editor. To enable labeling you will need an elevenlabs API key for speaker detection and transcription and to enable object tracking and other video based label you will need a google cloud project with the GCVI api enabled. Labeling gives context to your video library, allows for easier entity tagging and better search. Also if you choose to use the CLI it provides rich context for script or AI based editing. Notes First boot creates the superadmin via POCKETBASE_ADMIN_EMAIL / POCKETBASE_ADMIN_PASSWORD. This allows for access to the database admin, and these credentials are used by the backend worker to authenticate to the database. No built-in TLS. Put it behind your usual reverse proxy (Cloudflared / Caddy / Traefik) if you want https. If you have questions or issues, post them here – I'll do what I can to help, and others running it can chime in.
