[brencher] Migrate remaining configs from GitHub to self-hosted Gitea #18

Open
opened 2026-08-30 21:04:37 +02:00 by hermes · 0 comments
Contributor

Migrate brencher configs from GitHub to self-hosted Gitea

Sub-tickets (blocked by this parent)

  • #19 — Migrate gitea.py config to multi-remote
  • #20 — Migrate gmail_mcp.py config to multi-remote
  • #21 — Migrate hermes.py config to multi-remote
  • #22 — Migrate torrserv_proxy.py config to multi-remote

All four must be merged before this parent can be closed.

Context

Several brencher deployment configs in admin/brencher/backend/configs/ still clone the upstream repos from https://github.com/rudolf1/<repo>.git. After migrating the Gitea instance to gitea.rudolf.keenetic.link and creating admin/<repo> mirrors, the deployment pipeline should pull from there instead.

Already migrated

  • hermes_infra.py — done (PR #8: feat(configs): point hermes_infra at gitea admin/hermes ansible repos)
  • immich.py — done (PR #12: feat(configs): point immich at gitea admin/hermes ansible repos)
  • brencher.py, brencher2.py — already in the multi-remote form (github + gitea_admin + gitea_hermes), no action needed.

Out of scope (intentionally NOT migrated)

  • brencher_local1.py, brencher_local2.py — these are dev-loop configs that intentionally target the local checkout on github; per user direction they stay on GitHub.
  • registry.py — per user direction, stays on GitHub for now.

Remaining configs to migrate

The following configs still use the old single-remote pattern (GitClone(url="https://github.com/rudolf1/<repo>")) and need the multi-remote migration pattern that brencher.py/brencher2.py already established:

Config file Current upstream Target remotes
gitea.py github.com/rudolf1/uber_backup.git github + gitea_admin + gitea_hermes
gmail_mcp.py github.com/rudolf1/uber_backup.git github + gitea_admin + gitea_hermes
hermes.py github.com/rudolf1/uber_backup.git github + gitea_admin + gitea_hermes
torrserv_proxy.py github.com/rudolf1/reverseproxy.git github + gitea_admin + gitea_hermes

Migration pattern (already established in brencher.py/brencher2.py)

Replace:

clone = GitClone(url="https://github.com/rudolf1/<repo>.git")

with:

clone = GitClone(remotes=[
    {"name": "github",       "url": "https://github.com/rudolf1/<repo>.git"},
    {"name": "gitea_admin",  "url": "https://gitea.rudolf.keenetic.link/admin/<repo>"},
    {"name": "gitea_hermes", "url": "https://gitea.rudolf.keenetic.link/hermes/<repo>"},
])

This keeps github as a fallback source while making gitea_admin and gitea_hermes the authoritative sources — same pattern that already works for brencher.py and brencher2.py in production.

Acceptance criteria

  • All four target configs use the remotes=[...] multi-source form.
  • No config in the table above still points at a single github.com URL.
  • Each sub-ticket is closed with the merged PR link.
  • brencher_local1.py, brencher_local2.py, registry.py, hermes_infra.py, immich.py are left untouched (already in desired state or out of scope).
## Migrate brencher configs from GitHub to self-hosted Gitea ### Sub-tickets (blocked by this parent) - #19 — Migrate `gitea.py` config to multi-remote - #20 — Migrate `gmail_mcp.py` config to multi-remote - #21 — Migrate `hermes.py` config to multi-remote - #22 — Migrate `torrserv_proxy.py` config to multi-remote All four must be merged before this parent can be closed. ### Context Several `brencher` deployment configs in `admin/brencher/backend/configs/` still clone the upstream repos from `https://github.com/rudolf1/<repo>.git`. After migrating the Gitea instance to `gitea.rudolf.keenetic.link` and creating `admin/<repo>` mirrors, the deployment pipeline should pull from there instead. ### Already migrated - `hermes_infra.py` — done (PR #8: `feat(configs): point hermes_infra at gitea admin/hermes ansible repos`) - `immich.py` — done (PR #12: `feat(configs): point immich at gitea admin/hermes ansible repos`) - `brencher.py`, `brencher2.py` — already in the multi-remote form (`github` + `gitea_admin` + `gitea_hermes`), no action needed. ### Out of scope (intentionally NOT migrated) - `brencher_local1.py`, `brencher_local2.py` — these are dev-loop configs that intentionally target the local checkout on github; per user direction they stay on GitHub. - `registry.py` — per user direction, stays on GitHub for now. ### Remaining configs to migrate The following configs still use the old single-remote pattern (`GitClone(url="https://github.com/rudolf1/<repo>")`) and need the multi-remote migration pattern that `brencher.py`/`brencher2.py` already established: | Config file | Current upstream | Target remotes | |---|---|---| | `gitea.py` | `github.com/rudolf1/uber_backup.git` | `github` + `gitea_admin` + `gitea_hermes` | | `gmail_mcp.py` | `github.com/rudolf1/uber_backup.git` | `github` + `gitea_admin` + `gitea_hermes` | | `hermes.py` | `github.com/rudolf1/uber_backup.git` | `github` + `gitea_admin` + `gitea_hermes` | | `torrserv_proxy.py` | `github.com/rudolf1/reverseproxy.git` | `github` + `gitea_admin` + `gitea_hermes` | ### Migration pattern (already established in `brencher.py`/`brencher2.py`) Replace: ```python clone = GitClone(url="https://github.com/rudolf1/<repo>.git") ``` with: ```python clone = GitClone(remotes=[ {"name": "github", "url": "https://github.com/rudolf1/<repo>.git"}, {"name": "gitea_admin", "url": "https://gitea.rudolf.keenetic.link/admin/<repo>"}, {"name": "gitea_hermes", "url": "https://gitea.rudolf.keenetic.link/hermes/<repo>"}, ]) ``` This keeps `github` as a fallback source while making `gitea_admin` and `gitea_hermes` the authoritative sources — same pattern that already works for `brencher.py` and `brencher2.py` in production. ### Acceptance criteria - All four target configs use the `remotes=[...]` multi-source form. - No config in the table above still points at a single `github.com` URL. - Each sub-ticket is closed with the merged PR link. - `brencher_local1.py`, `brencher_local2.py`, `registry.py`, `hermes_infra.py`, `immich.py` are left untouched (already in desired state or out of scope).
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: admin/brencher#18