feat: deploy Gitea on HK node
This commit is contained in:
@@ -0,0 +1,17 @@
|
||||
# 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 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 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`.
|
||||
Reference in New Issue
Block a user