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>
67 lines
1.6 KiB
YAML
67 lines
1.6 KiB
YAML
app:
|
|
id: nostr-rs-relay
|
|
name: Nostr Relay (Rust)
|
|
version: 0.8.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: High-performance Nostr relay written in Rust. Host your own decentralized social media relay and earn networking profits.
|
|
|
|
container:
|
|
image: scsibug/nostr-rs-relay:0.8.9
|
|
image_signature: cosign://...
|
|
pull_policy: verify-signature
|
|
data_uid: "1000:1000"
|
|
|
|
dependencies:
|
|
- storage: 10Gi # For event storage
|
|
|
|
resources:
|
|
cpu_limit: 2
|
|
memory_limit: 1Gi
|
|
disk_limit: 10Gi
|
|
|
|
security:
|
|
capabilities: []
|
|
readonly_root: true
|
|
no_new_privileges: true
|
|
user: 1000
|
|
seccomp_profile: default
|
|
network_policy: isolated
|
|
apparmor_profile: nostr-relay
|
|
|
|
ports:
|
|
- host: 18081
|
|
container: 8080
|
|
protocol: tcp # HTTP/WebSocket
|
|
bind: 127.0.0.1
|
|
auth: gated
|
|
|
|
volumes:
|
|
- type: bind
|
|
source: /var/lib/archipelago/nostr-relay
|
|
target: /usr/src/app/db
|
|
options: [rw]
|
|
|
|
environment:
|
|
- RELAY_NAME=Archipelago Nostr Relay
|
|
- RELAY_DESCRIPTION=Self-hosted Nostr relay on Archipelago
|
|
- MAX_EVENTS=1000000
|
|
- MAX_SUBSCRIPTIONS=100
|
|
|
|
health_check:
|
|
type: http
|
|
endpoint: http://localhost:8080
|
|
path: /
|
|
interval: 30s
|
|
timeout: 30s
|
|
retries: 5
|
|
|
|
nostr_integration:
|
|
relay_type: public
|
|
monetization_enabled: true # Earn networking profits
|
|
event_storage: sqlite
|