archipelagoandClaude Opus 5
eb48eab946
Nodes offer an update when the signed catalog pins something newer than what's running, and that machinery is fine. The missing step was the one before it: nothing told *us* when upstream shipped. A pin could sit at fedimintd v0.10.0 for months while every node in the fleet correctly and confidently reported "up to date". The reason nothing could tell us is that a manifest records only our mirror — `source.archipelago-foundation.org/lfg2025/fedimintd:v0.10.0` says nothing about the project it was mirrored from. So this adds an optional `app.upstream` block naming the real source, and a script that asks each one what it has released. Running it answers the question that prompted this. Of 58 apps, 28 are behind, including LND v0.18.4-beta against v0.21.2-beta, Bitcoin Core 28.4 against 31.1, and fedimintd/gatewayd v0.10.0 against v0.10.1. Two choices worth stating. An app with no `upstream` block is reported as UNTRACKED rather than skipped — a silent skip is how this stayed invisible, and before this commit all 58 were silently skipped. And a suggestion prefers our own tag variant: telling someone pinned to `postgres:16.13-alpine` that the newest tag is `18.6-trixie` is true and useless, because swapping the base image is a different decision from bumping a version. Five apps are deliberately left untracked (barkd, immich-postgres, indeedhub-minio, lightning-stack, pine-whisper): I could not establish their upstream with confidence, and a wrong `repo` produces a confident wrong verdict, which is worse than an honest gap. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
61 lines
2.0 KiB
YAML
61 lines
2.0 KiB
YAML
app:
|
|
id: fips-ui
|
|
name: FIPS Mesh
|
|
version: 1.0.0
|
|
# Built by this project — there is no upstream release feed to watch.
|
|
upstream:
|
|
kind: internal
|
|
description: |
|
|
Archipelago-native dashboard for the FIPS mesh transport. Runs nginx
|
|
inside a container with host networking, serves a static dashboard on
|
|
:8336, and reverse-proxies /rpc/v1 to the archipelago backend on
|
|
127.0.0.1:5678. All FIPS controls (status, seed anchors, reconnect,
|
|
restart, and stable-channel daemon updates) go through the existing
|
|
fips.* RPC methods, authenticated by the browser's own archipelago
|
|
session — there is no separate secret to manage.
|
|
|
|
container:
|
|
build:
|
|
context: /opt/archipelago/docker/fips-ui
|
|
dockerfile: Dockerfile
|
|
tag: localhost/fips-ui:local
|
|
|
|
resources:
|
|
memory_limit: 128Mi
|
|
|
|
security:
|
|
readonly_root: false
|
|
network_policy: host
|
|
|
|
# Host networking: nginx listens on 8336 directly on the host IP and
|
|
# proxies to 127.0.0.1:5678 (the archipelago RPC). `ports:` is
|
|
# intentionally empty because host networking bypasses port mapping.
|
|
# Declared so the APP GATE can see this port. Host networking means Podman
|
|
# publishes nothing (quadlet skips PublishPort in host mode), so `bind:` here
|
|
# is a statement of where the container's own nginx listens — 127.0.0.1 —
|
|
# not a publish instruction. Without this declaration the gate had no idea
|
|
# the port existed: it was neither protected nor listed as unprotected, and
|
|
# served the FIPS mesh screen unauthenticated on every interface.
|
|
ports:
|
|
- host: 8336
|
|
container: 8336
|
|
protocol: tcp
|
|
bind: 127.0.0.1
|
|
auth: gated
|
|
# First-party companion UI: its nginx forwards the node session cookie
|
|
# to the daemon's authenticated endpoints; without passthrough the gate
|
|
# strips it and every data call 401s while the page shell renders.
|
|
session_passthrough: true
|
|
|
|
volumes: []
|
|
|
|
environment: []
|
|
|
|
health_check:
|
|
type: http
|
|
endpoint: http://127.0.0.1:8336
|
|
path: /
|
|
interval: 30s
|
|
timeout: 5s
|
|
retries: 3
|