fscotto/infra
1
0
Fork 0
mirror of https://github.com/fscotto/infra.git synced 2026-10-03 13:29:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document confirmed Gitea domain transition completion

Browse Source
This commit is contained in:
Fabio Scotto di Santolo
2026-10-03 15:15:21 +02:00
parent 269fb13665
commit 18eb2d2eb2
2 changed files with 18 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
AGENTS.md
View File

@@ -381,8 +381,12 @@ successfully. The first monthly scrub remains a runtime check.
HTTPS and authenticated SSH reads returned the same repository HEAD.
The new NPM hostnames passed TLS/HTTP checks; old DuckDNS Proxy Hosts were
observed disabled. Details are in `docs/domain-fscotto-co.md`.
- [ ] Confirm login on the new Gitea hostname and update remaining client remotes/integrations.
The operator confirmed SSH pull; transport/authentication work, but the agent did not test push.
- [x] Confirm login on the new Gitea hostname and update remaining client remotes/integrations.
The operator confirmed completion on 2026-10-03; the agent did not perform a test push.
- [x] Remove obsolete DuckDNS NPM Proxy Hosts, unused certificates and the old upstream override.
The operator confirmed completion on 2026-10-03; no new agent runtime check was performed.
- [x] Review and remove completed one-time procedures from the playbook.
The operator confirmed completion on 2026-10-03.
- [x] Retire Prometheus' local DuckDNS updater on 2026-10-03 through Ansible:
the five-minute cron entry and private updater/log directory were removed.
Provisioning is disabled; repeat cleanup changed nothing. HTTPS services, private NPM
@@ -454,7 +458,8 @@ successfully. The first monthly scrub remains a runtime check.
on 2026-10-03. Its NPM Proxy Host was already soft-deleted and had no
associated certificate. Its Ansible domain and runtime override were removed;
nginx -t and reload passed without restarting NPM. Primary HTTPS returned 200
with valid TLS; only `git.fscotto.duckdns.org` remains declared for Gitea.
with valid TLS. At that step only `git.fscotto.duckdns.org` remained declared;
the subsequent domain transition and operator-confirmed cleanup are tracked above.
- [ ] Observe the first scheduled export and Atlas pull after the cutover; the manual end-to-end
cycle passed, but the next unattended cycle has not yet occurred.

17
docs/domain-fscotto-co.md
View File

@@ -66,14 +66,17 @@ The repeat cleanup changed nothing; ordinary DuckDNS provisioning was skipped.
The cron table had no remaining entries, NPM and the export timer were active,
and NPM administration still listened only on `127.0.0.1:81`.
## Remaining transition work
## Operator-confirmed transition completion
- Confirm user-authenticated login and push on the new Gitea hostname.
- Update existing remotes and callback/webhook URLs explicitly.
- Retire obsolete NPM hosts/certificates and the old upstream override
after confirming they are no longer needed.
On 2026-10-03 the operator confirmed completion of:
At inspection the three old DuckDNS Proxy Hosts were already disabled,
not deleted. They are not working HTTPS rollback endpoints. Existing backup
- Web login on the new Gitea hostname.
- Updates to remaining Git remotes, webhooks and integrations.
- Removal of obsolete DuckDNS NPM Proxy Hosts, unused certificates and the old upstream override.
- Review and removal of completed one-time procedures from the playbook.
These are operator confirmations, not new agent runtime checks or a test push.
At the earlier inspection the three old DuckDNS Proxy Hosts were disabled,
not deleted; that observation predates the confirmed cleanup. Existing backup
archives remain preserved. DNS/Pages/NPM changes were operator actions;
the Gitea application configuration change was deployed through Ansible.