github.com is unreachable from the brencher container (squid returns HTTP 403 on CONNECT), and reverseproxy.git does not exist on gitea yet. The brencher deploy of the torrserv_proxy environment will fail until this is resolved.
What's needed
A gitea repo at admin/reverseproxy (and ideally a fork hermes/reverseproxy) containing:
all branches from https://github.com/rudolf1/reverseproxy.git
including the default branch
After the mirror exists, the follow-up PR in admin/brencher (feat/torrserv-proxy-gitea-remotes or similar) will switch the torrserv_proxy.py config to use GitClone(remotes=[...]) pointing at the new mirror.
Why this matters
This is blocking the torrserv_proxy 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. The only configs still blocked on a missing gitea mirror are torrserv_proxy (this one) and gmail_mcp (separate ticket).
Verification needed before closing
admin/reverseproxy exists and contains all branches from the github source
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/reverseproxy returns refs
Related
Separate ticket filed for gmail_mcp requiring rudolf1/uber_backup.git mirror
admin/ansible#1 inlines docker_socket_proxy + brencher-state-proxy into hermes_squid (unrelated but same workflow)
## Why
`backend/configs/torrserv_proxy.py` (in admin/brencher) currently uses:
```
clone = GitClone(url="https://github.com/rudolf1/reverseproxy.git")
```
`github.com` is unreachable from the brencher container (squid returns HTTP 403 on CONNECT), and `reverseproxy.git` does not exist on gitea yet. The brencher deploy of the `torrserv_proxy` environment will fail until this is resolved.
## What's needed
A gitea repo at `admin/reverseproxy` (and ideally a fork `hermes/reverseproxy`) containing:
- all branches from `https://github.com/rudolf1/reverseproxy.git`
- including the default branch
After the mirror exists, the follow-up PR in admin/brencher (`feat/torrserv-proxy-gitea-remotes` or similar) will switch the `torrserv_proxy.py` config to use `GitClone(remotes=[...])` pointing at the new mirror.
## Why this matters
This is blocking the torrserv_proxy 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. The only configs still blocked on a missing gitea mirror are `torrserv_proxy` (this one) and `gmail_mcp` (separate ticket).
## Verification needed before closing
1. `admin/reverseproxy` exists and contains all branches from the github source
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/reverseproxy` returns refs
## Related
- Separate ticket filed for `gmail_mcp` requiring `rudolf1/uber_backup.git` mirror
- admin/ansible#1 inlines docker_socket_proxy + brencher-state-proxy into hermes_squid (unrelated but same workflow)
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/torrserv_proxy.py(in admin/brencher) currently uses:github.comis unreachable from the brencher container (squid returns HTTP 403 on CONNECT), andreverseproxy.gitdoes not exist on gitea yet. The brencher deploy of thetorrserv_proxyenvironment will fail until this is resolved.What's needed
A gitea repo at
admin/reverseproxy(and ideally a forkhermes/reverseproxy) containing:https://github.com/rudolf1/reverseproxy.gitAfter the mirror exists, the follow-up PR in admin/brencher (
feat/torrserv-proxy-gitea-remotesor similar) will switch thetorrserv_proxy.pyconfig to useGitClone(remotes=[...])pointing at the new mirror.Why this matters
This is blocking the torrserv_proxy 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. The only configs still blocked on a missing gitea mirror aretorrserv_proxy(this one) andgmail_mcp(separate ticket).Verification needed before closing
admin/reverseproxyexists and contains all branches from the github sourcegit ls-remote https://gitea.rudolf.keenetic.link/admin/reverseproxyreturns refsRelated
gmail_mcprequiringrudolf1/uber_backup.gitmirror