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>
55 lines
1.5 KiB
YAML
55 lines
1.5 KiB
YAML
app:
|
|
id: indeedhub-ffmpeg
|
|
name: IndeedHub FFmpeg Worker
|
|
version: "1.0.0"
|
|
# Built by this project — there is no upstream release feed to watch.
|
|
upstream:
|
|
kind: internal
|
|
description: IndeedHub background media transcoding worker.
|
|
category: community
|
|
|
|
# Hyphen name matches runtime references + the live container (adoption). No
|
|
# network_alias: nothing connects TO the worker — it only dials out to
|
|
# postgres/redis/minio (resolved by their aliases on indeedhub-net).
|
|
container_name: indeedhub-ffmpeg
|
|
|
|
container:
|
|
image: source.archipelago-foundation.org/lfg2025/indeedhub-ffmpeg:1.0.0
|
|
pull_policy: if-not-present
|
|
network: indeedhub-net
|
|
secret_env:
|
|
- key: DATABASE_PASSWORD
|
|
secret_file: indeedhub-db-password
|
|
- key: AWS_SECRET_KEY
|
|
secret_file: indeedhub-minio-password
|
|
|
|
dependencies:
|
|
- app_id: indeedhub-api
|
|
|
|
resources:
|
|
memory_limit: 4Gi
|
|
|
|
security:
|
|
capabilities: []
|
|
readonly_root: false
|
|
network_policy: isolated
|
|
|
|
ports: []
|
|
|
|
volumes: []
|
|
|
|
environment:
|
|
- DATABASE_HOST=postgres
|
|
- DATABASE_PORT=5432
|
|
- DATABASE_USER=indeedhub
|
|
- DATABASE_NAME=indeedhub
|
|
- QUEUE_HOST=redis
|
|
- QUEUE_PORT=6379
|
|
- S3_ENDPOINT=http://minio:9000
|
|
- AWS_REGION=us-east-1
|
|
- AWS_ACCESS_KEY=indeeadmin
|
|
- S3_PUBLIC_BUCKET_NAME=indeedhub-public
|
|
- S3_PRIVATE_BUCKET_NAME=indeedhub-private
|
|
- ENVIRONMENT=production
|
|
- AES_MASTER_SECRET=0123456789abcdef0123456789abcdef
|