## Migrate `torrserv_proxy.py` config from GitHub to self-hosted Gitea
Part of parent: #18 ([brencher] Migrate remaining configs from GitHub to self-hosted Gitea).
### Current state
`admin/brencher/backend/configs/torrserv_proxy.py`:
```python
clone = GitClone(url="https://github.com/rudolf1/reverseproxy.git")
```
### Target state
Adopt the multi-remote pattern already used in `brencher.py` and `brencher2.py`. Note the upstream repo is `reverseproxy`, not `brencher`:
```python
clone = GitClone(remotes=[
{"name": "github", "url": "https://github.com/rudolf1/reverseproxy.git"},
{"name": "gitea_admin", "url": "https://gitea.rudolf.keenetic.link/admin/reverseproxy"},
{"name": "gitea_hermes", "url": "https://gitea.rudolf.keenetic.link/hermes/reverseproxy"},
])
```
### Acceptance criteria
- `torrserv_proxy.py` uses `GitClone(remotes=[...])` with the three remotes above.
- No behavior change for `stack_name="torrserv_proxy"` (downstream of `clone`).
- Single-purpose PR in `admin/brencher` referencing this issue.
- Closes #18 sub-task when merged.
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
torrserv_proxy.pyconfig from GitHub to self-hosted GiteaPart of parent: #18 ([brencher] Migrate remaining configs from GitHub to self-hosted Gitea).
Current state
admin/brencher/backend/configs/torrserv_proxy.py:Target state
Adopt the multi-remote pattern already used in
brencher.pyandbrencher2.py. Note the upstream repo isreverseproxy, notbrencher:Acceptance criteria
torrserv_proxy.pyusesGitClone(remotes=[...])with the three remotes above.stack_name="torrserv_proxy"(downstream ofclone).admin/brencherreferencing this issue.Linked to parent #18. Related work: #19, #20, #21, #22.