24 lines
1.1 KiB
Markdown
24 lines
1.1 KiB
Markdown
# HK Gitea
|
|
|
|
Gitea target on the `bwh-hk-cmi` Arcane Environment.
|
|
|
|
- Web: `https://gitea.kais.cloud`
|
|
- Git SSH: `ssh://git@gitea.kais.cloud:222/<owner>/<repo>.git`
|
|
- Persistent data: `/opt/stacks/gitea/data`
|
|
- Shared reverse-proxy network: external Docker network `hk-web`
|
|
- Reverse proxy: Caddy in the existing `web-managed` project
|
|
|
|
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.
|