archipelagoandClaude Opus 5
c19c411b91
With registry push access, the 24 mirror-backed apps stopped being blocked. Ten images are now mirrored (single-platform amd64, matching the existing convention) and their pins moved: alby-hub v1.23.0 -> v1.24.0 mempool-frontend v3.0.1 -> v3.3.1 (mempool, archy-mempool-web) mempool-backend v3.0.0 -> v3.3.1 fedimintd v0.10.0 -> v0.10.1 gatewayd v0.10.0 -> v0.10.1 nostr-rs-relay 0.9.0 -> 0.10.0 portainer 2.39.1 -> 2.39.6 vaultwarden 1.30.0-alpine -> 1.37.1-alpine jellyfin 10.8.13 -> 10.11.11 home-assistant 2026.7.3 -> 2026.8.2 Every one verified pullable from our mirror after copying, so none can become an image-not-found on a node. image-versions.sh moved in lockstep — it is the baseline the update badge compares against when the catalog does not cover an app, and leaving it behind would have kept advertising an update that had already been applied. Chosen by risk, not by count: these are patch/minor bumps with no data migration. The ones held back are held for a reason each — Postgres 15->18 and 16->18 refuse to start on an older cluster, Redis 7->8, Valkey 7->9, Nextcloud 29->32 must go one major at a time, plus uptime-kuma 1->2, grafana 10->13, electrumx 1->2, photoprism, and core-lightning's three years of schema migrations. Those are each a migration plan, not a pin edit. LND (v0.18.4 -> v0.21.2) is held separately: it is only a minor bump by version but it migrates its channel database irreversibly, and this box holds real funds. Note the checker still reports several of these as behind, and that is correct: it reads the *catalog* pin, which is what nodes actually act on. These land when the catalog is regenerated and re-signed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
54 lines
1.3 KiB
YAML
54 lines
1.3 KiB
YAML
app:
|
|
id: indeedhub-relay
|
|
name: IndeedHub Nostr Relay
|
|
version: "0.9.0"
|
|
# Where this app comes from, so scripts/check-upstream-releases.py can
|
|
# tell us when the pin below has fallen behind. Without it nothing can:
|
|
# container.image names our mirror, not the project it was mirrored from.
|
|
upstream:
|
|
kind: github
|
|
repo: scsibug/nostr-rs-relay
|
|
description: nostr-rs-relay backing IndeedHub's Nostr identity + comments.
|
|
category: community
|
|
|
|
# Hyphen name matches runtime references + the live container (adoption);
|
|
# alias `relay` is the short hostname the frontend nginx proxies to
|
|
# (http://relay:8080 for the /relay websocket).
|
|
container_name: indeedhub-relay
|
|
|
|
container:
|
|
image: source.archipelago-foundation.org/lfg2025/nostr-rs-relay:0.10.0
|
|
pull_policy: if-not-present
|
|
network: indeedhub-net
|
|
network_aliases: [relay]
|
|
|
|
dependencies:
|
|
- storage: 2Gi
|
|
|
|
resources:
|
|
memory_limit: 256Mi
|
|
disk_limit: 2Gi
|
|
|
|
security:
|
|
capabilities: []
|
|
readonly_root: false
|
|
network_policy: isolated
|
|
|
|
ports: []
|
|
|
|
# Named volume matches the live indeedhub-relay-data volume on .228.
|
|
volumes:
|
|
- type: volume
|
|
source: indeedhub-relay-data
|
|
target: /usr/src/app/db
|
|
options: [rw]
|
|
|
|
environment: []
|
|
|
|
health_check:
|
|
type: tcp
|
|
endpoint: localhost:8080
|
|
interval: 30s
|
|
timeout: 5s
|
|
retries: 3
|