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>
66 lines
1.9 KiB
YAML
66 lines
1.9 KiB
YAML
app:
|
|
id: indeedhub-postgres
|
|
name: IndeedHub Postgres
|
|
version: "16.13-alpine"
|
|
# 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: dockerhub
|
|
repo: library/postgres
|
|
description: Postgres database backend for IndeedHub.
|
|
category: community
|
|
|
|
# Container named indeedhub-postgres (hyphen) to match the runtime's existing
|
|
# per-app references (health_monitor tiers/deps, crash_recovery) and the live
|
|
# .228 install, so the orchestrator ADOPTS the running container instead of
|
|
# recreating it. `network_aliases: [postgres]` keeps the short hostname the
|
|
# api/ffmpeg/relay reach by (DATABASE_HOST=postgres) resolvable on
|
|
# indeedhub-net, reproducing the legacy `--network-alias postgres`.
|
|
container_name: indeedhub-postgres
|
|
|
|
container:
|
|
image: source.archipelago-foundation.org/lfg2025/postgres:16.13-alpine
|
|
pull_policy: if-not-present
|
|
network: indeedhub-net
|
|
network_aliases: [postgres]
|
|
generated_secrets:
|
|
- name: indeedhub-db-password
|
|
kind: hex32
|
|
secret_env:
|
|
- key: POSTGRES_PASSWORD
|
|
secret_file: indeedhub-db-password
|
|
|
|
dependencies:
|
|
- storage: 10Gi
|
|
|
|
resources:
|
|
memory_limit: 1Gi
|
|
disk_limit: 10Gi
|
|
|
|
security:
|
|
capabilities: [CHOWN, DAC_OVERRIDE, FOWNER, SETGID, SETUID]
|
|
readonly_root: false
|
|
network_policy: isolated
|
|
|
|
ports: []
|
|
|
|
# Named podman volume (matches the live indeedhub-postgres-data volume on .228);
|
|
# preserves all existing database content across the migration.
|
|
volumes:
|
|
- type: volume
|
|
source: indeedhub-postgres-data
|
|
target: /var/lib/postgresql/data
|
|
options: [rw]
|
|
|
|
environment:
|
|
- POSTGRES_USER=indeedhub
|
|
- POSTGRES_DB=indeedhub
|
|
|
|
health_check:
|
|
type: tcp
|
|
endpoint: localhost:5432
|
|
interval: 30s
|
|
timeout: 5s
|
|
retries: 3
|