Document staged Gitea migration to Atlas

This commit is contained in:
Fabio Scotto di Santolo
2026-10-01 21:10:32 +02:00
parent 802cb8c7ba
commit 5b0f415163
4 changed files with 104 additions and 0 deletions

View File

@@ -260,6 +260,13 @@ successfully. The first monthly scrub remains a runtime check.
### Priority 3 - Service expansion
- [ ] After data protection and recovery are validated, populate `/zpool/media/music` and validate Navidrome.
- [x] Design the staged Prometheus-to-Atlas Gitea migration in `docs/atlas-gitea-migration.md`.
The approved topology keeps NPM on Prometheus and moves HTTPS and public SSH (TCP/2222) together;
the existing rootful image/data layout is retained. No data has been moved or traffic changed.
- [ ] Prepare a separate Atlas Gitea dataset, disabled Quadlet, and isolated restore test from the
verified Prometheus backup; validate SQLite, repositories, SSH host keys, and target backups.
- [ ] After an explicit outage approval, perform the final consistent copy and HTTPS/SSH cutover,
then remove Gitea from Prometheus' desired stack and backup export without deleting source data.
- [ ] Design and deploy Nextcloud as another explicitly temporary Atlas service before Uranus. Give it
separate persistent application, database, and cache storage; keep credentials in Vault; publish it only
through NPM over the Prometheus--Aegis gateway; and define backup, upgrade, and eventual Uranus-migration