github.com is unreachable from the brencher container (squid returns HTTP 403 on CONNECT), and uber_backup.git does not exist on gitea yet. The brencher deploy of the gmail_mcp environment will fail until this is resolved.
What's needed
A gitea repo at admin/uber_backup (and ideally a fork hermes/uber_backup) containing:
all branches from https://github.com/rudolf1/uber_backup.git
including the immoscout branch (the one referenced via branchNamePrefix)
After the mirror exists, the follow-up PR in admin/brencher (feat/gmail-mcp-gitea-remotes or similar) will switch the gmail_mcp.py config to use GitClone(remotes=[...]) pointing at the new mirror.
Why this matters
This is blocking the gmail_mcp config from being deployable. The other ansible-targeting configs (registry, gitea, hermes, immich, hermes_infra, docker_socket_proxy) have already been migrated to use the existing admin/ansible + hermes/ansible gitea mirrors via PR #3-style remotes=[...]. The only configs still blocked on a missing gitea mirror are gmail_mcp (this one) and torrserv_proxy (separate ticket).
Verification needed before closing
admin/uber_backup exists and contains all branches from the github source, including immoscout
brencher-bot has at least read access (push access preferred for cross-fork PRs)
A test clone from inside the brencher container (with the proxy) succeeds: git ls-remote https://gitea.rudolf.keenetic.link/admin/uber_backup returns refs including refs/heads/immoscout
Related
admin/brencher#4 (closed, see related context) was the first attempt at adding the docker_socket_proxy config — its clone line uses the same url= form, migrated in admin/brencher#9..#12
admin/ansible#1 inlines docker_socket_proxy + brencher-state-proxy into hermes_squid
## Why
`backend/configs/gmail_mcp.py` (in admin/brencher) currently uses:
```
clone = GitClone(url="https://github.com/rudolf1/uber_backup.git", branchNamePrefix="immoscout")
```
`github.com` is unreachable from the brencher container (squid returns HTTP 403 on CONNECT), and `uber_backup.git` does not exist on gitea yet. The brencher deploy of the `gmail_mcp` environment will fail until this is resolved.
## What's needed
A gitea repo at `admin/uber_backup` (and ideally a fork `hermes/uber_backup`) containing:
- all branches from `https://github.com/rudolf1/uber_backup.git`
- including the `immoscout` branch (the one referenced via `branchNamePrefix`)
After the mirror exists, the follow-up PR in admin/brencher (`feat/gmail-mcp-gitea-remotes` or similar) will switch the `gmail_mcp.py` config to use `GitClone(remotes=[...])` pointing at the new mirror.
## Why this matters
This is blocking the gmail_mcp config from being deployable. The other ansible-targeting configs (registry, gitea, hermes, immich, hermes_infra, docker_socket_proxy) have already been migrated to use the existing `admin/ansible` + `hermes/ansible` gitea mirrors via PR #3-style remotes=[...]. The only configs still blocked on a missing gitea mirror are `gmail_mcp` (this one) and `torrserv_proxy` (separate ticket).
## Verification needed before closing
1. `admin/uber_backup` exists and contains all branches from the github source, including `immoscout`
2. brencher-bot has at least read access (push access preferred for cross-fork PRs)
3. A test clone from inside the brencher container (with the proxy) succeeds: `git ls-remote https://gitea.rudolf.keenetic.link/admin/uber_backup` returns refs including `refs/heads/immoscout`
## Related
- admin/brencher#4 (closed, see related context) was the first attempt at adding the docker_socket_proxy config — its `clone` line uses the same `url=` form, migrated in admin/brencher#9..#12
- admin/ansible#1 inlines docker_socket_proxy + brencher-state-proxy into hermes_squid
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.
Why
backend/configs/gmail_mcp.py(in admin/brencher) currently uses:github.comis unreachable from the brencher container (squid returns HTTP 403 on CONNECT), anduber_backup.gitdoes not exist on gitea yet. The brencher deploy of thegmail_mcpenvironment will fail until this is resolved.What's needed
A gitea repo at
admin/uber_backup(and ideally a forkhermes/uber_backup) containing:https://github.com/rudolf1/uber_backup.gitimmoscoutbranch (the one referenced viabranchNamePrefix)After the mirror exists, the follow-up PR in admin/brencher (
feat/gmail-mcp-gitea-remotesor similar) will switch thegmail_mcp.pyconfig to useGitClone(remotes=[...])pointing at the new mirror.Why this matters
This is blocking the gmail_mcp config from being deployable. The other ansible-targeting configs (registry, gitea, hermes, immich, hermes_infra, docker_socket_proxy) have already been migrated to use the existing
admin/ansible+hermes/ansiblegitea mirrors via PR #3-style remotes=[...]. The only configs still blocked on a missing gitea mirror aregmail_mcp(this one) andtorrserv_proxy(separate ticket).Verification needed before closing
admin/uber_backupexists and contains all branches from the github source, includingimmoscoutgit ls-remote https://gitea.rudolf.keenetic.link/admin/uber_backupreturns refs includingrefs/heads/immoscoutRelated
cloneline uses the sameurl=form, migrated in admin/brencher#9..#12