¶ Prereqs And Decisions
Date: 2026-02-06
This is the list of information we must collect before we make any system changes.
- How Gitea is deployed:
docker compose file OR docker run command OR systemd unit(s).
- Gitea version.
- Data directory location (the mounted
/data path on the host).
- Database type:
- SQLite vs Postgres vs MySQL/MariaDB.
- If external DB: host, port, db name (no credentials in docs).
- Current external URLs:
- HTTP(S) base URL users use.
- SSH clone URL and SSH port (if used).
- Integrations:
- Webhooks in use.
- OAuth/SSO.
- SMTP.
- LFS.
- Packages/registry.
- Actions usage (if any).
- Namespace name:
- Domain/hostname for Gitea:
- Example:
gitea.auth.home.lan.
- TLS strategy:
- Static TLS secret provided manually, or
- cert-manager (adds complexity).
- SSH strategy:
- If SSH clones are required: pick
NodePort or hostPort approach.
- Database:
- External Postgres (preferred) or in-cluster Postgres.
- Backups:
- Where backups are stored (NFS share, another host, or object storage if available locally).
- GitOps:
- Argo CD installation namespace:
argocd.
- Argo managed repos: at least one “cluster apps” repo.
- Confirm the Kubernetes cluster is stable and the ingress controller is healthy.
- Confirm storage capacity on
drg-k8s.auth.home.lan for PVCs.
- Confirm DNS and routing for new hostnames.
- Confirm firewall/router rules if using SSH NodePort.