Run Tuvima Library as a Container Manager project using a complete Compose file. The project keeps the app configuration together for later updates.
Allow 10–20 minutes for folder and container setup, plus image and model downloads. Follow the NAS documentation for your installed software version.
Tuvima Library uses the published ghcr.io/tuvima/tuvima-library:latest image. If the NAS cannot download it, use the local source-build path and load that image on the NAS before creating the project.
Prepare folders
Create a shared folder tree such as:
/volume1/docker/tuvima/config/volume1/docker/tuvima/db/volume1/docker/tuvima/models/volume1/docker/tuvima/artwork-cache/volume1/docker/tuvima/backups/volume1/docker/tuvima/transcodeChoose the media paths that will become your managed or read-only library sources. Give the service account represented by TUVIMA_UID and TUVIMA_GID access to every mapped folder. You can obtain a user’s numeric IDs over an administrator SSH session with id USERNAME.
Create the project
- Download the complete maintained configuration from the Docker guide into a project folder on the NAS.
- Replace the Unraid-style
/mnt/user/...example paths with/volume1/...paths that exist on this NAS. - Set the numeric UID/GID and
TZ. - In Container Manager → Project, choose Create.
- Name the project
tuvima, select its working directory, and upload or paste the Compose file. - Build and start the project.
Wait for tuvima-library to report healthy, then open http://NAS-IP:5016/setup, complete setup directly, and save the generated recovery codes.
Do not add a port mapping for 61495. Use the Synology reverse proxy only for Dashboard port 5016, and follow the trusted-proxy and TLS steps in Operations and Recovery.
See Synology’s official Container Manager Project documentation for DSM-specific project controls.
Keep all persistent folders
Retain mappings for /library, /config, /db, /models, /artwork-cache, /backups, and /transcode. Reuse them when updating the container. An existing read-only media folder needs a separate mapping.
Claim your server
First-run setup is open to any device that can reach the server until the first administrator exists, so finish it before you open any router port.
- Open
/setupfrom any device on your home network. No setup code is needed. - Once the administrator exists, setup closes for good.