Files

T

Frank c99eb8e11b docs(fleet): live-probe corrections across dankclaw, caddy, gitea, searxng, vpn docs

Live read-only probes on Dankclaw (BatchMode ssh, 2026-10-19):

- system/dankclaw.md: full 32-container census added (authentik IdP,
  prometheus/grafana/loki/alloy/alertmanager monitoring, pihole, ntfy,
  seerr, hermes stack, anubis, frank-tts :7772 all undocumented);
  dragoon pool corrected 401,408 @ ctx 200,704 (was conflated);
  zealot corrected to PrismML build 10777, Ternary-Bonsai-2-9B
  PQ2_0-MTP, 2x262,144 over one 524,288 pool, f16 K+V (doc claimed
  build 10754, 27B, 2x200,704)
- caddy/index.md: v2.11.7 (in-container ), deduped
  caddyfile listing
- gitea: version 1.27.3 probed via API; systemd-gitea network + rootless
  100999 mapping confirmed live (gitea-server attaches systemd-gitea;
  dank subuid 100000:65536); index See-Also de-duplicated
- searxng-tuning.md: live instance section (ghcr image, valkey:9-alpine,
  marreta netns-sharing explains duplicate port maps); POLICY DRIFT FLAG:
  tuned engine policy (google/bing disabled, verified 2026-08-16) is NOT
  live — /config now shows all 262 engines enabled; upstream settings.yml
  count corrected 388@master; limiter table already matched source
- vpn-routing.md: verify snippet fixed — gluetun image ships no curl;
  health server is 127.0.0.1:9999/health ('OK'), :8000 is the CONTROL
  server (404s on health paths); correct probes provided

Refs #29

2026-10-19 04:12:04 -07:00

3.4 KiB

Raw Blame History

Gitea on dankclaw

Private Git hosting on dankclaw. Two quadlet-managed containers in the rootless podman session of user dank: Gitea and PostgreSQL, sharing a dedicated network unit. The former gitea-caddy container is retired — the canonical fleet Caddy (caddy.service, see /caddy/index.md) fronts gitea.franksdank.cloud; do not recreate the retired unit.

Host: dankclaw (192.168.0.143 LAN) Config: ~/.config/containers/systemd/gitea-{postgres,server}.container + gitea.network Local access: http://dankclaw:3000 — Gitea 1.27.3 (/api/v1/version, probed 2026-10-19) Domain: https://gitea.franksdank.cloud (live; served by fleet Caddy, DNS-01 TLS)

Architecture

Container	Unit	Port	Purpose
`gitea-server`	`gitea-server.service`	3000 (HTTP), 2222 (SSH)	Git web UI, API, SSH daemon
`gitea-postgres`	`gitea-postgres.service`	5432 (internal)	Database
(network)	`gitea-network.service`	—	quadlet `gitea.network` bring-up

The containers share the private network systemd-gitea (quadlet gitea.network, DNS enabled). The automatic podman default network has DNS disabled; do not run the stack on it.

Management

All commands run as dank on dankclaw.

Action	Command
Start all	`systemctl --user start gitea-postgres gitea-server`
Stop all	`systemctl --user stop gitea-server gitea-postgres`
Restart Gitea only	`systemctl --user restart gitea-server`
Follow logs	`podman logs -f gitea-server` or `journalctl --user -u gitea-server -f`
Check status	`systemctl --user status gitea-postgres gitea-server`

Data Persistence

All data lives on host bind mounts under /home/dank/Containers/gitea/ (fleet storage standard since 2026-09-01; verified live 2026-10-18). Containers are ephemeral. Stopping a quadlet unit removes its container; the next start recreates it. Volumes survive. The old /opt/gitea/ tree remains on disk as a leftover — do not use it.

Path	Contents
`/home/dank/Containers/gitea/data/`	Git repositories, app.ini, attachments
`/home/dank/Containers/gitea/postgres/`	PostgreSQL data files
`/home/dank/Containers/gitea/env`	EnvironmentFile (mode 0600; `GITEA_DB_PASSWORD`)

See data-persistence for backup and restore.

Boot Persistence

User-level linger is enabled for dank. The units start at host boot without a login. Each unit carries [Install] WantedBy=default.target; the podman generator applies it. The legacy podman-compose stack had no units and did not survive reboots (incident 2026-08-16).

See management for boot persistence details and troubleshooting.

Repo Copies

The quadlet files and .env templates are tracked in the serverAppConfigs deploy repo; the sibling vault page Infrastructure/Gitea.md (in ~/Projects/serverAppConfig/serverAppConfigs-docs/) is the deploy-side source of truth. Secrets live only on the host under Containers/gitea/ (mode 0600), never in either docs tree.

3.4 KiB Raw Blame History