Own the MokoGitea deploy workflows (dev/rc/prod) as canonical synced source #3

New Issue

2026-07-05T23:33:13Z

jmiller commented

2026-07-05 23:33:13 +00:00

Move the MokoGitea server deploy workflows into Template-Go so they're the canonical, version-controlled source that syncs to the Go server repo(s), instead of being hand-maintained in the fork's custom/ (where they're safe from sync overwrite but also not shared/tracked centrally).

Workflows to own

Currently in MokoConsulting/MokoGitea-Fork/.mokogitea/workflows/custom/:

deploy-dev.yml — build+deploy on push to dev → mokogitea-dev (port 3090, DB mokogitea_dev), git.dev.mokoconsulting.tech
deploy-rc.yml (new, MokoGitea-Fork#751) — build+deploy on push to rc → mokogitea-rc (port 3110, DB mokogitea_rc), rc.git.mokoconsulting.tech
deploy-mokogitea.yml — production deploy → mokogitea (DB mokogitea), git.mokoconsulting.tech

Pipeline they implement

dev (continuous, on push) → rc (on promote-rc / PR-to-main) → prod (stable). The prod gate should require RC healthy (not dev). Channels: stable > release-candidate > … > development.

Notes

These are MokoGitea-server-specific (they deploy the Gitea instances), so they likely belong in a Go-server overlay or a dedicated section of Template-Go — parameterize host/ports/DB/container names where reasonable so they're not hardcoded to one deployment.
All three now use the fixed deploy pattern: ${MOKOGITEA_*_TAG} env-var driving the shared compose (no sed), docker rm -f before --force-recreate, quoted-heredoc remote expansion, health check + external verify.
After moving here, the fork's custom/ copies should be removed so the synced versions win (avoid two sources of truth).
Recent context: DB + user renamed to mokogitea* across prod/dev/rc; RC environment stood up with Let's Encrypt.

Related: MokoGitea-Fork#751 (deploy-rc), Template-Generic#71 (release-notes workflow work).

https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

Move the MokoGitea server deploy workflows into Template-Go so they're the **canonical, version-controlled source** that syncs to the Go server repo(s), instead of being hand-maintained in the fork's `custom/` (where they're safe from sync overwrite but also not shared/tracked centrally). ## Workflows to own Currently in `MokoConsulting/MokoGitea-Fork/.mokogitea/workflows/custom/`: - `deploy-dev.yml` — build+deploy on push to `dev` → `mokogitea-dev` (port 3090, DB `mokogitea_dev`), git.dev.mokoconsulting.tech - **`deploy-rc.yml`** (new, MokoGitea-Fork#751) — build+deploy on push to `rc` → `mokogitea-rc` (port 3110, DB `mokogitea_rc`), rc.git.mokoconsulting.tech - `deploy-mokogitea.yml` — production deploy → `mokogitea` (DB `mokogitea`), git.mokoconsulting.tech ## Pipeline they implement `dev` (continuous, on push) → `rc` (on promote-rc / PR-to-main) → `prod` (stable). The prod gate should require **RC healthy** (not dev). Channels: stable > release-candidate > … > development. ## Notes - These are MokoGitea-server-specific (they deploy the Gitea instances), so they likely belong in a Go-**server** overlay or a dedicated section of Template-Go — parameterize host/ports/DB/container names where reasonable so they're not hardcoded to one deployment. - All three now use the fixed deploy pattern: `${MOKOGITEA_*_TAG}` env-var driving the shared compose (no `sed`), `docker rm -f` before `--force-recreate`, quoted-heredoc remote expansion, health check + external verify. - After moving here, the fork's `custom/` copies should be removed so the synced versions win (avoid two sources of truth). - Recent context: DB + user renamed to `mokogitea*` across prod/dev/rc; RC environment stood up with Let's Encrypt. Related: MokoGitea-Fork#751 (deploy-rc), Template-Generic#71 (release-notes workflow work). https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT

jmiller referenced this issue from a commit

2026-07-06 01:19:36 +00:00

feat(ci): own MokoGitea deploy workflows (dev/rc/prod) as canonical synced source

Sign in to join this conversation.

Priority Medium

Type Feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/Template-Go#3