Skip to content
DiscVaultDiscVault Docs

Install: First start and health check

Goal and result

Section titled “Goal and result”

Verify startup and create the first owner only after the correct channel reports healthy.

Applies to

Section titled “Applies to”

Stable uses the established Passkey first-owner flow on host port 6080. The canonical beta Compose deployment uses host port 6180 and offers either Passkeys on a valid HTTPS FQDN or Legacy Authentication when its two-layer gate is enabled.

DiscVault v26 stable

Section titled “DiscVault v26 stable”
  • DiscVault v26 stable · ghcr.io/helmerznl/discvault:latest
  • Passkey first-owner flow · host 6080 → internal API 5000

DiscVault v26 beta

Section titled “DiscVault v26 beta”
  • DiscVault v26 beta · ghcr.io/helmerznl/discvault:beta
  • Passkey or Legacy Authentication first-owner flow
  • host 6180 → internal API 5000

Prerequisites

Section titled “Prerequisites”
  • running v26 deployment
  • browser · configured origin

Procedure

Section titled “Procedure”
  1. Inspect: Compose status · postgres health · startup logs
  2. Verify: GET /api/next/health · HTTP 2xx
  3. Choose: Passkey owner · Install: Legacy Authentication
  4. Open: configured origin · first Owner
  5. Verify: Owner · GET /api/next/auth/status · WebAuthn or password + TOTP

Commands and settings

Section titled “Commands and settings”

DiscVault v26 stable

Section titled “DiscVault v26 stable”
Terminal window
docker compose --env-file /opt/discvault/.env -p discvault -f /opt/discvault/compose.yaml ps
docker compose --env-file /opt/discvault/.env -p discvault -f /opt/discvault/compose.yaml logs --tail=100 next-api next-worker next-mcp postgres
curl --fail http://localhost:6080/api/next/health
curl --fail http://localhost:6080/api/next/auth/status

DiscVault v26 beta

Section titled “DiscVault v26 beta”
Terminal window
docker compose -p discvault_next_deploy -f /opt/discvault-next/docker-compose.yml ps
docker compose -p discvault_next_deploy -f /opt/discvault-next/docker-compose.yml logs --tail=100 next-api next-worker next-mcp postgres
curl --fail http://localhost:6180/api/next/health
curl --fail http://localhost:6180/api/next/auth/status

Expected result

Section titled “Expected result”

Health returns success, the configured origin opens, and the first account becomes Owner through the selected Passkey or beta password-plus-TOTP route.

  • health succeeds, the configured origin opens, and the first account is the owner

Safety and rollback

Section titled “Safety and rollback”

Next step

Section titled “Next step”

Update and migrate: Backup

Source and status

Section titled “Source and status”