dvb-projekt/warppool-umbrel-official
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
dvb-WarpPool app folder in the official Umbrel App Store format — copy-ready for getumbrel/umbrel-apps
2 commits 1 branch 0 tags 37 KiB
Find a file
Exact
dvb-projekt 02ee03203a dvb-warppool 1.25.0 — re-pin to the current release 
Digest verified against the registry before pinning (multi-arch amd64 +
arm64). The comparison table no longer names the community store's version
number — it drifted the moment the next release landed, and the point of
that row is tag-vs-digest, not the number.
2026-07-30 08:54:29 +02:00
dvb-warppool dvb-warppool 1.25.0 — re-pin to the current release 2026-07-30 08:54:29 +02:00
README.md dvb-warppool 1.25.0 — re-pin to the current release 2026-07-30 08:54:29 +02:00

README.md

dvb-WarpPool — official Umbrel App Store submission files

This repo holds only the app folder for the official Umbrel App Store, in the format getumbrel/umbrel-apps expects. It is meant to be copied in as-is:

dvb-warppool/
├── docker-compose.yml
├── umbrel-app.yml
├── config/.gitkeep
└── data/.gitkeep

It is deliberately not the same as our community store (git.warppool.org/dvb-projekt/dvb-projekt-Umbrel-Community-App-Store), which uses the 3333/34254/3334 host ports, a floating image tag and an init-chown service. Everything in the list below is the official-store variant.

What is different from the community store

community store this folder
Stratum host ports 3333 / 34254 / 3334 18335 / 18336 / 18337 (app's 188xx range)
image floating tag (:1.25.0 today) digest-pinned :1.25.0@sha256:5c44…33b9
config/ + data/ created by an init service running as root .gitkeep committed, no init service — umbrelOS creates them as 1000:1000
gallery / releaseNotes populated empty (lint requires this for a new app submission)
manifestVersion 1.1 1

Review points from June 2026 — all still in place

  1. No PROXY_AUTH_ADD: "false". Umbrel auth (and 2FA) covers the first-run setup wizard and /api/auth/bootstrap. Without it a LAN client could claim the admin account before the owner did. The dashboard widget still works — umbreld polls web:18334/api/umbrel-widget internally over Docker DNS, so no PROXY_AUTH_WHITELIST is needed.
  2. No init-chown service in this variant — config/ and data/ ship with a .gitkeep, umbrelOS creates them as 1000:1000 and web runs as 1000:1000.
  3. No .cookie bind-mount. RPC goes through APP_BITCOIN_RPC_USER / APP_BITCOIN_RPC_PASS, which umbrelOS always provides.

Three things you may want to change

  1. submission: still points at getumbrel/umbrel-apps#5780. That PR is a 404 now — the GitHub account dvb-projekt was suspended (crypto ToS classifier; nothing in the PR itself was the trigger). Please repoint it at whatever PR you open.
  2. The ${APP_BITCOIN_DATA_DIR}:/bitcoin:ro mount is the only line that was not in the version you reviewed. It exists for the opt-in IPC block template backend on Core ≥ 31 (same directory-mount pattern sv2-ui uses — the socket is resolved inside, never bind-mounted itself). It is read-only and unused with the default gbt template source, but it does make the node's wallet and cookie files readable to this container. Deleting that one line disables IPC and removes the exposure; everything else keeps working. Your call — happy to ship it either way.
  3. The image lives in our own registry (git.warppool.org), anonymous pull, multi-arch amd64 + arm64, signed with our cosign key (cosign.pub in the main repo). If a mirror somewhere else would make you more comfortable, say the word.

Verify the pin

docker manifest inspect git.warppool.org/dvb-projekt/dvb-warppool:1.25.0

Index digest as of 2026-07-30: sha256:5c442c67ec0ef4f9e1c5f7ece0a9487121072352cef9f5241b2eb7dbd04d33b9 (linux/amd64 + linux/arm64).

Source, releases and docs: https://git.warppool.org/dvb-projekt/dvb-WarpPool · https://docs.warppool.org · https://warppool.org