Skip to content
DiscVaultDiscVault Docs

Reference

Goal and result

Section titled “Goal and result”

Look up image channels, ports, endpoints, persistent data locations, and channel-specific environment keys.

Applies to

Section titled “Applies to”

ghcr.io/helmerznl/discvault:latest is DiscVault v26 stable and ghcr.io/helmerznl/discvault:beta is DiscVault v26 beta. They share one PostgreSQL-backed architecture; only the image tag differs. :dev is engineering-only.

DiscVault v26 stable

Section titled “DiscVault v26 stable”
  • DiscVault v26 stable · ghcr.io/helmerznl/discvault:latest
  • PostgreSQL + /data
  • API 6080:5000 + MCP 6090:6090

DiscVault v26 beta

Section titled “DiscVault v26 beta”
  • DiscVault v26 beta · ghcr.io/helmerznl/discvault:beta
  • PostgreSQL + /data
  • API 6080:5000 + MCP 6090:6090

Prerequisites

Section titled “Prerequisites”
  • selected release channel

Procedure

Section titled “Procedure”
  1. Inspect: running image digest · :latest / :beta
  2. Record: :dev is engineering-only and not a release channel; DiscVault v26 stable uses :latest and DiscVault v26 beta uses :beta · :dev
  3. Record: ports + /api/next/health + passkey keys
  4. Record: PostgreSQL + /data · matched backup method

Expected result

Section titled “Expected result”

An operator can identify the running channel and all data that must be backed up before a change.

  • selected release channel · @sha256:
  • :latest · :beta · :dev

Safety and rollback

Section titled “Safety and rollback”

Next step

Section titled “Next step”

Start: Overview

Source and status

Section titled “Source and status”