Repo switched: uber_backup → mcps (the gmail + telegram MCP server repo, now mirrored on gitea under both admin/ and hermes/).
GitHub remote dropped: matches the pattern in hermes_infra.py after #8 and docker_socket_proxy.py after #23. The brencher container cannot reach github.com (squid returns HTTP 403 on CONNECT tunnel), so keeping a github remote would hard-fail the clone and trap brencher in the same retry loop that blocked #23 on admin/reverseproxy before its mirror was created.
branchNamePrefix="immoscout" dropped: the prefix is only applied to remotes named origin (see backend/steps/git.py ~L104); neither remote qualifies, so the field is a silent no-op. Matches the cleanup done in hermes_infra.py / brencher.py.
## Summary
Updates `backend/configs/gmail_mcp.py` to point at the new `mcps` stack mirrors on gitea instead of the legacy `uber_backup` repo.
Remotes now:
- `gitea_hermes` → `https://gitea.rudolf.keenetic.link/hermes/mcps`
- `gitea_admin` → `https://gitea.rudolf.keenetic.link/admin/mcps`
Uses the `remotes=[{name, url}, …]` form introduced by #3.
## What changed vs the original #26 body
- **Repo switched**: `uber_backup` → `mcps` (the gmail + telegram MCP server repo, now mirrored on gitea under both `admin/` and `hermes/`).
- **GitHub remote dropped**: matches the pattern in `hermes_infra.py` after #8 and `docker_socket_proxy.py` after #23. The brencher container cannot reach `github.com` (squid returns HTTP 403 on CONNECT tunnel), so keeping a `github` remote would hard-fail the clone and trap brencher in the same retry loop that blocked #23 on `admin/reverseproxy` before its mirror was created.
- **`branchNamePrefix="immoscout"` dropped**: the prefix is only applied to remotes named `origin` (see `backend/steps/git.py` ~L104); neither remote qualifies, so the field is a silent no-op. Matches the cleanup done in `hermes_infra.py` / `brencher.py`.
## Diff (vs `main`)
```diff
-clone = GitClone(url="https://github.com/rudolf1/uber_backup.git", branchNamePrefix="immoscout")
+clone = GitClone(remotes=[
+ {"name": "gitea_hermes", "url": "https://gitea.rudolf.keenetic.link/hermes/mcps"},
+ {"name": "gitea_admin", "url": "https://gitea.rudolf.keenetic.link/admin/mcps"},
+])
```
## Prerequisites (already done)
Both target mirrors exist on gitea:
- `admin/mcps` — already present (primary, not a fork).
- `hermes/mcps` — forked in this session (id=10, fork of `admin/mcps`).
## Test plan
1. From the brencher state file for `gmail_mcp`, register `gitea_hermes/feat/migrate-gmail-mcp-to-multi-remote` as the desired branch.
2. Watch brencher logs: `Cloning repositories [...]` should succeed for both `gitea_hermes` and `gitea_admin`.
3. Confirm `gmail_mcp` stack redeploys against the new repo.
Refs #20
Part of #18
Migrates backend/configs/gmail_mcp.py from the legacy single-remote
url= form to the remotes=[{name, url}, ...] form introduced by #3.
Source repo is rudolf1/uber_backup; branchNamePrefix='immoscout' is
preserved (only applies to remotes named 'origin', so it's a no-op
here, matching the pattern used by hermes_infra.py and brencher.py).
Refs #20
Rebase of the original #26 swap onto the new stack mirrors:
- gitea_hermes -> gitea.rudolf.keenetic.link/hermes/mcps
- gitea_admin -> gitea.rudolf.keenetic.link/admin/mcps
Drops the github remote for the same reason as hermes_infra.py after
PR #8 -- brencher cannot reach github.com (squid returns HTTP 403 on
CONNECT tunnel), so a github remote would hard-fail the clone and trap
brencher in the same retry loop that blocked #23 on reverseproxy.
Drops branchNamePrefix='immoscout': the prefix is only applied to
remotes named 'origin' (backend/steps/git.py ~L104); neither remote
qualifies, so the field is a silent no-op. Matches hermes_infra.py /
brencher.py pattern.
Refs #20
Part of #18
hermes
changed title from feat(configs): point gmail_mcp at gitea admin/hermes repos to feat(configs): point gmail_mcp at gitea admin/hermes mcps repos2026-09-05 16:39:03 +02:00
admin/mcps uses a single root-level docker-compose.yml with two
services (gmail-mcp-server + telegram-mcp-server) sharing one
network and secrets block. The previous path
'gmail-mcp-server/docker-compose.yml' was the layout in
github.com/rudolf1/uber_backup (where the stack originally lived
in a subdirectory) and breaks DockerComposeBuild /
DockerSwarmDeploy against the new mcps repo.
Refs #20
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.
Summary
Updates
backend/configs/gmail_mcp.pyto point at the newmcpsstack mirrors on gitea instead of the legacyuber_backuprepo.Remotes now:
gitea_hermes→https://gitea.rudolf.keenetic.link/hermes/mcpsgitea_admin→https://gitea.rudolf.keenetic.link/admin/mcpsUses the
remotes=[{name, url}, …]form introduced by #3.What changed vs the original #26 body
uber_backup→mcps(the gmail + telegram MCP server repo, now mirrored on gitea under bothadmin/andhermes/).hermes_infra.pyafter #8 anddocker_socket_proxy.pyafter #23. The brencher container cannot reachgithub.com(squid returns HTTP 403 on CONNECT tunnel), so keeping agithubremote would hard-fail the clone and trap brencher in the same retry loop that blocked #23 onadmin/reverseproxybefore its mirror was created.branchNamePrefix="immoscout"dropped: the prefix is only applied to remotes namedorigin(seebackend/steps/git.py~L104); neither remote qualifies, so the field is a silent no-op. Matches the cleanup done inhermes_infra.py/brencher.py.Diff (vs
main)Prerequisites (already done)
Both target mirrors exist on gitea:
admin/mcps— already present (primary, not a fork).hermes/mcps— forked in this session (id=10, fork ofadmin/mcps).Test plan
gmail_mcp, registergitea_hermes/feat/migrate-gmail-mcp-to-multi-remoteas the desired branch.Cloning repositories [...]should succeed for bothgitea_hermesandgitea_admin.gmail_mcpstack redeploys against the new repo.Refs #20
Part of #18
Migrates backend/configs/gmail_mcp.py from the legacy single-remote url= form to the remotes=[{name, url}, ...] form introduced by #3. Source repo is rudolf1/uber_backup; branchNamePrefix='immoscout' is preserved (only applies to remotes named 'origin', so it's a no-op here, matching the pattern used by hermes_infra.py and brencher.py). Refs #20445209d5c3toa747f9e790feat(configs): point gmail_mcp at gitea admin/hermes reposto feat(configs): point gmail_mcp at gitea admin/hermes mcps repos32dbe6dfbdto6fd598983a