#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)
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).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Migrate brencher configs from GitHub to self-hosted Gitea
Sub-tickets (blocked by this parent)
gitea.pyconfig to multi-remotegmail_mcp.pyconfig to multi-remotehermes.pyconfig to multi-remotetorrserv_proxy.pyconfig to multi-remoteAll four must be merged before this parent can be closed.
Context
Several
brencherdeployment configs inadmin/brencher/backend/configs/still clone the upstream repos fromhttps://github.com/rudolf1/<repo>.git. After migrating the Gitea instance togitea.rudolf.keenetic.linkand creatingadmin/<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 thatbrencher.py/brencher2.pyalready established:gitea.pygithub.com/rudolf1/uber_backup.gitgithub+gitea_admin+gitea_hermesgmail_mcp.pygithub.com/rudolf1/uber_backup.gitgithub+gitea_admin+gitea_hermeshermes.pygithub.com/rudolf1/uber_backup.gitgithub+gitea_admin+gitea_hermestorrserv_proxy.pygithub.com/rudolf1/reverseproxy.gitgithub+gitea_admin+gitea_hermesMigration pattern (already established in
brencher.py/brencher2.py)Replace:
with:
This keeps
githubas a fallback source while makinggitea_adminandgitea_hermesthe authoritative sources — same pattern that already works forbrencher.pyandbrencher2.pyin production.Acceptance criteria
remotes=[...]multi-source form.github.comURL.brencher_local1.py,brencher_local2.py,registry.py,hermes_infra.py,immich.pyare left untouched (already in desired state or out of scope).