Install: Installation routes

Goal and result

Choose the DiscVault v26 topology for new installs, or keep an existing previous-generation deployment on the frozen Legacy image until migration.

Applies to

ghcr.io/helmerznl/discvault:latest is DiscVault v26 stable and ghcr.io/helmerznl/discvault:beta is DiscVault v26 beta. The official app/deploy/next/docker-compose.yml and .env.example procedure is beta-only and uses DISCVAULT_NEXT_IMAGE; the advanced Docker-run procedure remains available for both channels. The frozen ghcr.io/helmerznl/discvault:legacy image is only for an existing previous-generation installation that is not ready to migrate. Never substitute that deployment image into the v26 beta topology.

DiscVault v26 stable

DiscVault v26 stable · ghcr.io/helmerznl/discvault:latest
select the procedure whose channel metadata matches the running image
PostgreSQL 17 + persistent /data

DiscVault v26 beta

DiscVault v26 beta · ghcr.io/helmerznl/discvault:beta
select the procedure whose channel metadata matches the running image
PostgreSQL 17 + persistent /data

Prerequisites

Docker Engine 24+
Docker Compose v2

Procedure

Choose: Install: Docker Compose · official DiscVault 26 beta deployment files
Choose: Install: Docker run · advanced stable or beta equivalent
Choose: Install: Unraid · Unraid Compose Manager
Choose: new installations use DiscVault v26 :latest or :beta; only an existing previous-generation installation that is not ready to migrate should use the frozen :legacy image
Preserve: keep the previous generation’s volumes, environment variables, ports, and data path unchanged; never substitute :legacy into the v26 PostgreSQL Compose topology
Open: Update and migrate: DiscVault 26 migration · existing data → DiscVault 26
Record: DISCVAULT_IMAGE · image digest · existing or legacy deployment only: matching backup set

Task routes

Install: Docker Compose — DiscVault 26 beta · official release/v26-beta files · DISCVAULT_NEXT_IMAGE
Install: Docker run — DiscVault 26 · Docker run · PostgreSQL + /data · DATABASE_URL
Install: Persistent data and PostgreSQL — DiscVault 26 · PostgreSQL + /data
Install: Unraid — DiscVault 26 · Unraid · PostgreSQL + /data
Update and migrate: DiscVault 26 migration — previous generation → DiscVault 26 · guarded import

Expected result

A new install selects one v26 channel, while an existing previous-generation install either stays on its unchanged Legacy topology or follows the migration procedure.

selected release channel
PostgreSQL + /data · both v26 channels
keep the previous generation’s volumes, environment variables, ports, and data path unchanged; never substitute :legacy into the v26 PostgreSQL Compose topology