From 6ca7093cebfbed782c1165e0bdf98949858a06a9 Mon Sep 17 00:00:00 2001 From: Codex Date: Sun, 6 Sep 2026 04:42:51 -0700 Subject: [PATCH] fix: lock HK Gitea bootstrap --- servers/bwh-hk-cmi/gitea/README.md | 4 +++- servers/bwh-hk-cmi/gitea/compose.yaml | 4 ++++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/servers/bwh-hk-cmi/gitea/README.md b/servers/bwh-hk-cmi/gitea/README.md index 6b151f3..37dcd7c 100644 --- a/servers/bwh-hk-cmi/gitea/README.md +++ b/servers/bwh-hk-cmi/gitea/README.md @@ -10,7 +10,9 @@ Gitea target on the `bwh-hk-cmi` Arcane Environment. 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. +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 Gitea data directory is not stored in Git. Back it up before upgrades and before every migration attempt. Repository credentials, session secrets, and diff --git a/servers/bwh-hk-cmi/gitea/compose.yaml b/servers/bwh-hk-cmi/gitea/compose.yaml index f0b041a..67dea1a 100644 --- a/servers/bwh-hk-cmi/gitea/compose.yaml +++ b/servers/bwh-hk-cmi/gitea/compose.yaml @@ -12,6 +12,10 @@ services: GITEA__server__SSH_PORT: "222" GITEA__server__SSH_LISTEN_PORT: "22" GITEA__server__LFS_START_SERVER: "true" + GITEA__database__DB_TYPE: sqlite3 + GITEA__database__PATH: /data/gitea/gitea.db + GITEA__security__INSTALL_LOCK: "true" + GITEA__service__DISABLE_REGISTRATION: "true" ports: - "222:22" volumes: