VibraVid ghcr.io/astraelabs/vibravid:latest https://github.com/AstraeLabs/VibraVid/pkgs/container/vibravid bridge bash false https://github.com/AstraeLabs/VibraVid/issues https://github.com/AstraeLabs/VibraVid VibraVid - Web UI for managing video downloads. IMPORTANT: run the one-time setup script BELOW before first start, otherwise the container will crash. The Django source code and the SQLite database share the same directory in the upstream image (/app/GUI), so we cannot bind-mount that directory - we bind-mount only the db.sqlite3 file. The Conf directory holds only data files and is mounted normally. ONE-TIME SETUP (run on Unraid CLI before first start): mkdir -p /mnt/user/appdata/vibravid/Conf /mnt/user/appdata/vibravid/logs /mnt/user/downloads/vibravid docker pull ghcr.io/astraelabs/vibravid:latest docker create --name vv-seed ghcr.io/astraelabs/vibravid:latest docker cp vv-seed:/app/Conf/config.json /mnt/user/appdata/vibravid/Conf/config.json docker cp vv-seed:/app/Conf/login.json /mnt/user/appdata/vibravid/Conf/login.json docker rm vv-seed touch /mnt/user/appdata/vibravid/db.sqlite3 chown -R 1000:1000 /mnt/user/appdata/vibravid /mnt/user/downloads/vibravid CAVEAT: SQLite writes a transient journal file alongside db.sqlite3 during transactions. Because only the .sqlite3 file is bind-mounted (not its parent dir), the journal lives in the container's ephemeral layer. A hard kill mid-write could in theory leave the database in an inconsistent state. Avoid "Force Stop" and back up /mnt/user/appdata/vibravid/db.sqlite3 periodically. BACKUPS: cp /mnt/user/appdata/vibravid/db.sqlite3 /mnt/user/backups/vibravid-db-$(date +%F).sqlite3 MediaApp:Video Downloaders: http://[IP]:[PORT:8000] https://raw.githubusercontent.com/yusseiin/unraid-templates/main/img/vibravid.png 8000 /mnt/user/downloads/vibravid /mnt/user/appdata/vibravid/Conf /mnt/user/appdata/vibravid/db.sqlite3 /mnt/user/appdata/vibravid/logs change-me-to-a-secure-key localhost,127.0.0.1 http://localhost:8000,http://127.0.0.1:8000 false