DiscVault

DiscVault Launcher is an Unraid deployment manager that runs and updates the PostgreSQL-backed DiscVault 26 stack from a single container.

  • Infrastructure
  • Media Servers
  • Tools & Utilities
DiscVault Launcher is an Unraid deployment manager that runs and updates the PostgreSQL-backed DiscVault 26 stack from a single container. It orchestrates the full service stack — PostgreSQL, Next.js API, background worker, and MCP components — behind an Nginx reverse proxy, giving homelab users a managed DiscVault installation through Unraid Community Apps without manual Docker Compose configuration.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

47/100 Fair

Maintained
82last commit 15 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 22 days ago

GitHub stars
0
Open issues
0
Last commit
2026-11-06
License
MIT
Activity
stale

Checked 7 days ago - source: GitHub (helmerzNL/DiscVault-Launcher)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Image tags and channels Use ghcr.io/helmerznl/discvault-launcher:latest for the production release or :beta for the beta channel. The older :v26-beta and :v26 tags still work as aliases but should be migrated; :dev, :stable, and :legacy tags are no longer published. source
  • Install with Unraid Community Apps Install from Unraid Community Apps; the single launcher container deploys the full DiscVault stack (PostgreSQL, Next.js API, worker, and MCP) behind Nginx. source

Fetched 17 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does the DiscVault Launcher publish extra host ports for the internal API, worker, and MCP containers?

No. In launcher mode the managed containers do not bind their own host ports; the launcher remains the public endpoint and proxies / to next-api:5000 and /mcp to next-mcp:6090.

Which environment variables must I edit before running the standalone Docker Compose stack?

Copy .env.example to .env and edit POSTGRES_PASSWORD, JWT_SECRET, RP_ID, and RP_ORIGINS before running docker compose up -d.

How do I point the stack at an existing DiscVault data directory?

Set DISCVAULT_DATA_DIR to the existing directory, such as /mnt/user/appdata/discvault. DiscVault Next then reads /data/discvault.db and existing media folders through the migration UI.

Which DiscVault Launcher image tags should I use now?

Use latest for production or beta for the beta channel. Older v26-beta and v26 tags still work as aliases but should be migrated, while dev, stable, and legacy tags are no longer published.

What launcher config file should I keep stable for stack secrets?

Keep /config/stack.env stable because it contains the PostgreSQL password and JWT secret. It is not authoritative for image selection; DISCVAULT_CHANNEL and DISCVAULT_IMAGE are read from the container environment.

Answers sourced from ca.unraid.net, github.com

Community

Collected 48 days ago - public community threads