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>
108 lines
3.0 KiB
YAML
108 lines
3.0 KiB
YAML
app:
|
|
id: gitea
|
|
name: Gitea
|
|
version: "1.23"
|
|
# 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: go-gitea/gitea
|
|
description: Self-hosted Git service with built-in container registry, CI/CD, and package hosting.
|
|
category: development
|
|
|
|
container:
|
|
image: docker.io/gitea/gitea:1.23
|
|
pull_policy: if-not-present
|
|
|
|
dependencies:
|
|
- storage: 500Mi
|
|
|
|
resources:
|
|
memory_limit: 256Mi
|
|
disk_limit: 500Mi
|
|
|
|
security:
|
|
capabilities: [CHOWN, FOWNER, SETUID, SETGID, DAC_OVERRIDE, NET_BIND_SERVICE]
|
|
readonly_root: false
|
|
no_new_privileges: false
|
|
network_policy: bridge
|
|
|
|
ports:
|
|
- host: 3001
|
|
container: 3000
|
|
protocol: tcp
|
|
bind: 127.0.0.1
|
|
# open, not gated: Gitea carries a complete login of its own, and git
|
|
# clients speak HTTP basic-auth — a cookie challenge in front of
|
|
# git-over-HTTP breaks every clone/push. The gate still fronts the
|
|
# port (iframe header fixes, retry page, Tor); the operator can force
|
|
# the dashboard login back on from Settings → Gitea → Access control.
|
|
auth: open
|
|
auth_rationale: >-
|
|
Gitea enforces its own account login on every page and API route;
|
|
git clients authenticate with basic-auth/tokens and cannot complete
|
|
a browser login challenge.
|
|
- host: 2222
|
|
container: 22
|
|
protocol: tcp
|
|
auth: none
|
|
auth_rationale: >-
|
|
Git over SSH, authenticated by the user's own SSH keypair. Not HTTP, so the gate cannot serve a login page here.
|
|
|
|
volumes:
|
|
- type: bind
|
|
source: /var/lib/archipelago/gitea/data
|
|
target: /data
|
|
options: [rw]
|
|
- type: bind
|
|
source: /var/lib/archipelago/gitea/config
|
|
target: /etc/gitea
|
|
options: [rw]
|
|
|
|
environment:
|
|
- GITEA__database__DB_TYPE=sqlite3
|
|
- GITEA__server__SSH_PORT=2222
|
|
- GITEA__server__SSH_LISTEN_PORT=22
|
|
- GITEA__server__LFS_START_SERVER=true
|
|
- GITEA__packages__ENABLED=true
|
|
- GITEA__repository__ENABLE_PUSH_CREATE_USER=true
|
|
- GITEA__repository__ENABLE_PUSH_CREATE_ORG=true
|
|
|
|
health_check:
|
|
type: http
|
|
endpoint: http://localhost:3000
|
|
path: /
|
|
interval: 120s
|
|
timeout: 30s
|
|
retries: 5
|
|
|
|
interfaces:
|
|
main:
|
|
name: Web UI
|
|
description: Gitea web interface
|
|
type: ui
|
|
port: 3001
|
|
protocol: http
|
|
path: /
|
|
|
|
metadata:
|
|
icon: /assets/img/app-icons/gitea.svg
|
|
repo: https://gitea.com
|
|
tier: optional
|
|
launch:
|
|
open_in_new_tab: true
|
|
features:
|
|
- Git repositories with web UI
|
|
- Built-in container/package registry
|
|
- Issue tracking and pull requests
|
|
- CI/CD via Gitea Actions
|
|
- Lightweight SQLite deployment
|
|
|
|
nginx_proxy:
|
|
listen: 3000
|
|
proxy_pass: http://127.0.0.1:3001
|
|
extra_headers:
|
|
- proxy_hide_header X-Frame-Options
|
|
- proxy_hide_header Content-Security-Policy
|