Skip to content

Commit 8445254

Browse files
committed
docs(anubis): explain how to protect more than one service
Review question: one Anubis instance fronts a single TARGET. Document the two ways around that (extra anubis@<name> instances, or a Host-routing proxy as TARGET).
1 parent 1fbdf58 commit 8445254

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

‎json/anubis.json‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,10 @@
4848
"text": "The container is configured for direct exposure over plain HTTP (COOKIE_SECURE=false, USE_REMOTE_ADDRESS=true). When you put a TLS reverse proxy in front of it, set COOKIE_SECURE=true and remove USE_REMOTE_ADDRESS so client IPs come from X-Forwarded-For.",
4949
"type": "info"
5050
},
51+
{
52+
"text": "One Anubis instance protects one TARGET. For another service, copy /etc/anubis/main.env to /etc/anubis/<name>.env with its own BIND, METRICS_BIND and TARGET and run `systemctl enable --now anubis@<name>`. Alternatively point TARGET at a reverse proxy that routes by Host header and a single instance covers all its sites.",
53+
"type": "info"
54+
},
5155
{
5256
"text": "Bot policies live in /etc/anubis/main.botPolicies.yaml (a copy of the upstream default). Prometheus metrics are exposed on port 9090.",
5357
"type": "info"

0 commit comments

Comments
 (0)