mirror of
https://github.com/TecharoHQ/anubis.git
synced 2025-09-13 22:58:14 -04:00

* add docs site based on docusarus Closes #2 Signed-off-by: Xe Iaso <me@xeiaso.net> * docs: deploy to aeacus Signed-off-by: Xe Iaso <me@xeiaso.net> * ready for merge Signed-off-by: Xe Iaso <me@xeiaso.net> * docs: fix anubis port Signed-off-by: Xe Iaso <me@xeiaso.net> --------- Signed-off-by: Xe Iaso <me@xeiaso.net>
35 lines
923 B
Plaintext
35 lines
923 B
Plaintext
---
|
|
title: When using Caddy with Gitea/Forgejo
|
|
---
|
|
|
|
Gitea/Forgejo relies on the reverse proxy setting the `X-Real-Ip` header. Caddy does not do this out of the gate. Modify your Caddyfile like this:
|
|
|
|
```python
|
|
ellenjoe.int.within.lgbt {
|
|
# ...
|
|
# diff-remove
|
|
reverse_proxy http://localhost:3000
|
|
# diff-add
|
|
reverse_proxy http://localhost:3000 {
|
|
# diff-add
|
|
header_up X-Real-Ip {remote_host}
|
|
# diff-add
|
|
}
|
|
# ...
|
|
}
|
|
```
|
|
|
|
Ensure that Gitea/Forgejo have `[security].REVERSE_PROXY_TRUSTED_PROXIES` set to the IP ranges that Anubis will appear from. Typically this is sufficient:
|
|
|
|
```ini
|
|
[security]
|
|
REVERSE_PROXY_TRUSTED_PROXIES = 127.0.0.0/8,::1/128
|
|
```
|
|
|
|
However if you are running Anubis in a separate Pod/Deployment in Kubernetes, you may have to adjust this to the IP range of the Pod space in your Container Networking Interface plugin:
|
|
|
|
```ini
|
|
[security]
|
|
REVERSE_PROXY_TRUSTED_PROXIES = 10.192.0.0/12
|
|
```
|