archipelagoandClaude Fable 5
58cdea5e79
Demo images / Build & push demo images (push) Successful in 3m33s
Some apps carry a complete account system and are broken by an upstream challenge: git clients speak basic-auth (not browser cookies), and a BTCPay checkout link handed to a customer must open for that customer. Both were behind the gate's login page — the "non-browser clients need an access token" gap disclosed in five consecutive releases. - New manifest port policy `auth: open`: the daemon still fronts the port exactly like `gated` (loopback pin, external binds, frame-header fixes, app-down retry page, Tor upstream) but serves it without the login challenge. Requires auth_rationale, same burden of proof as `none`. Gitea 3001 and BTCPay 23000 declare it. - Runtime operator override per app (security.set-app-gate → app-configs/ <id>.json "gateEnabled"), surfaced as Settings → app → Access control. Wins over the manifest in both directions and applies on the next request — no restart, and it works today on catalog-covered apps whose signed manifest still says `gated`. - The gate resolves policy per-request from the live port map, so a toggle takes effect without waiting for the 60s rebind sweep. "Off" never releases the port: gated apps are loopback-pinned, so releasing would strand them, not open them. - security.app-gate-status now reports gate_enabled + any override. - New guard test pins the `auth: open` set (both entries reviewed); the `auth: none` count moves 25 → 26, absorbing pre-existing drift from the phoenixd onboarding (loopback JSON API with its own generated password). - Docs: the manifest spec's ports row documented only host/container/ protocol — bind, auth, auth_rationale and session_passthrough were undocumented. Added a full "Ports & the app gate" section plus a developer-guide entry telling app authors to enforce their own auth regardless, since the operator can flip the gate either way. Verified live on archi-dev-box from an external address: gated → 401 gate page; override off → Gitea 200 own page, BTCPay 302 to its own login, git-over-HTTP info/refs 200; override on → 401 again; clear → default. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
102 lines
2.7 KiB
YAML
102 lines
2.7 KiB
YAML
app:
|
|
id: gitea
|
|
name: Gitea
|
|
version: "1.23"
|
|
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
|