kai/infra-docker-configs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record completed Gitea data migration

Browse Source
This commit is contained in:
Codex
2026-09-06 21:58:31 -07:00
parent 6ca7093ceb
commit 65cad02473
1 changed files with 9 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
servers/bwh-hk-cmi/gitea/README.md
+9 -5
View File
@@ -8,12 +8,16 @@ Gitea target on the `bwh-hk-cmi` Arcane Environment.
- Shared reverse-proxy network: external Docker network `hk-web`
- Reverse proxy: Caddy in the existing `web-managed` project
The initial target deliberately uses Gitea `1.25.1`, matching the source on
Arcane Local Docker. Keep the source online and do not initialize unrelated
production data before the planned dump/restore cutover. The target uses
SQLite with `INSTALL_LOCK` enabled and registration disabled so the public
endpoint cannot be claimed while it is waiting for the source restore.
The target deliberately uses Gitea `1.25.1`, matching the former source on
Arcane Local Docker. The complete source data set was cold-copied on
2026-09-06; the former source container remains stopped as a rollback point.
The migrated instance uses SQLite with `INSTALL_LOCK` enabled and registration
disabled.
The Gitea data directory is not stored in Git. Back it up before upgrades and
before every migration attempt. Repository credentials, session secrets, and
the migrated `app.ini` remain only under `/opt/stacks/gitea/data`.
The centralized Arcane repository record and existing project remotes still
use the former Tailnet URL. Change and regression-test those URLs in a separate
phase; the data migration itself does not imply a client cutover.